The image resize feature implemented in "image_resize.php"
cannot calculate the effective size of the resized image.
Furthermore every resized image is generated dynamically even
if the client already requested the same image with the same dimensions.
With a cache feature the image resize script could temporally
create the file on the disk to calculate it's effective size.
A caching algorithm could safe a lot of CPU time if images don't need to
be resized several times.
The index.php/wpws should inform the user about the cache state.
Original issue reported on code.google.com by 0x1010...@gmail.com on 3 Feb 2010 at 10:18
Original issue reported on code.google.com by
0x1010...@gmail.com
on 3 Feb 2010 at 10:18