You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you expected to see, versus what you actually saw
When we enable Dianoga on our production environment with an empty media cache, we see the CPU and memory consumption of the Azure WebApp go up to 100%. This could be caused by the Dianoga OptimizingMediaCache adding a thread for every non optimized image to a threadpool, and the WebApp is probably suffering from thread starvation causing our site to not respond to requests. Is it possible to implement a TPL to limit the number of concurrent tasks? Instead of passing the optimization process to a threadpool an actionblock could be used to limit the performance impact.
The text was updated successfully, but these errors were encountered:
Version of Dianoga
5.1.0
Environment description
Sitecore 9.0.2 on Azure WebApp S3
What configs you have enabled
Dianoga.DisableForSites
Dianoga.Jpeg
Dianoga.Png
Dianoga.Strategy.MediaCacheAsync
What you expected to see, versus what you actually saw
When we enable Dianoga on our production environment with an empty media cache, we see the CPU and memory consumption of the Azure WebApp go up to 100%. This could be caused by the Dianoga OptimizingMediaCache adding a thread for every non optimized image to a threadpool, and the WebApp is probably suffering from thread starvation causing our site to not respond to requests. Is it possible to implement a TPL to limit the number of concurrent tasks? Instead of passing the optimization process to a threadpool an actionblock could be used to limit the performance impact.
The text was updated successfully, but these errors were encountered: