Yes, it can slow down the site with excess memory use, unnecessary cpu cycles for re-creating thumbnails that already exist and should have been found in the cache, and by using more disk space for cached images than it really needs.
You should see an improvement with 2.2. If not, it may not be ImageGen that is the problem. On slow pages, use the ?umbDebugShowTrace=true querystring parameter to see the timing of your site and help pinpoint where the slowness originates. Of course, it could also be a server the is overloaded or insufficient bandwidth as well.
How does the imageGen 2.0.1 cache problem show.
Hi mighty forum.
We have a solution that ran with the 2.0.1 version of imagegen and we have had reports of the site running slow.
We have now upgraded to the 2.2.1 of imageGen and hopes this solves the issues we have seen.
Could a slow site be caused by the 2.0.1 version? What happened when the problem occured
Best regards
Yes, it can slow down the site with excess memory use, unnecessary cpu cycles for re-creating thumbnails that already exist and should have been found in the cache, and by using more disk space for cached images than it really needs.
You should see an improvement with 2.2. If not, it may not be ImageGen that is the problem. On slow pages, use the ?umbDebugShowTrace=true querystring parameter to see the timing of your site and help pinpoint where the slowness originates. Of course, it could also be a server the is overloaded or insufficient bandwidth as well.
cheers,
doug.
Thanks for the elaboration Douglas. We are still monitoring the 2.2 upgrade to see if it made a difference
Best Regards
Kristian
is working on a reply...