yappa-ng Extended Setup Information

Cache resized images

Do you want to cache the resized images for faster performance?

I can only recommend this option, because the program gets much faster if the images are cached, especially the image preview!!!
I personally use cache on all systems!

On the other hand you have to decide how much harddisk-storage-room you have at your disposal. If you enable this option every resized image gets saved to disk once.

One example:
If you have 4 different resize sizes defined (640, 800, 1024 and 1600) in the setup and all sizes get viewed you have the same image 7 times on the harddisk!

A very important factor for the needed harddisk-space is the "Resize Quality" (for jpgs!!) you will define later. These values are taken for a jpg image with a "Resize Quality" of 60%.

I think this will be absolute no issue if its your own server, but could lead to trouble if this is a hosted homepage at the server of your ISP.
Check the performance in both cases and if possible use the cache!


One more comment:
The resizing is only done on demand. The first one who looks at a photo does the resizing. The resizing is done only for the viewed resize-size. If for example the photo is never viewed in 1600 than there will be no cached image of the 1600 resolution!


Be sure to read the &qout;[More Info ... ]" of the "JPG Resize Qulity" and the "Permit Initialize Resize" for more information too!


--> Recommended setting for yappa-ng is: "yes"





Part of yappa-ng Documentation by Fritz 'wizard' Berger: >> yappa-ng Homepage <<