Recently I migrated a website from v8 to V10 and I'm facing performance issues in response time when accessing /media/ items (hosted on blob storage)
With Umbraco V8 the avg response time for media items was under 100ms
With Umbraco V10 the avg response time is between 1 to 2 seconds, sometimes it takes up to 30 seconds to load an image.
The website is hosted in Azure and using Blob storage (standard 2) for media items.
On UmbracoV8 it used Blob storage for media storage, BUT the cached items (crops) were hosted in the local storage of the App Service instead.
With Umbraco V10 both media and cache are stored in blob storage.
The website has many media items, here the numbers:
47.3k items in media folder
87.6k items in cache folder
Does anyone have experience with websites that have such a big media storage on azure? Any performance issues?
No reason and no solution found so far.
We now configured the website to use local storage for crops cache and use blob storage only for media storage.
But media requests are still very slow some times.
The next thing we'll try is to delete unused medias to clean up the blob storage, maybe with less items it will get faster
No, i didn't get any response. We've found out that the issue is most likely caused by the Umbraco.StorageProviders.AzureBlob package since it is using IFileProvider and this doesn't allow for async calls. And this might cause waiting requests if you get to many at once.
U10 - Blob storage for media very slow
Recently I migrated a website from v8 to V10 and I'm facing performance issues in response time when accessing /media/ items (hosted on blob storage)
With Umbraco V8 the avg response time for media items was under 100ms With Umbraco V10 the avg response time is between 1 to 2 seconds, sometimes it takes up to 30 seconds to load an image.
The website is hosted in Azure and using Blob storage (standard 2) for media items.
On UmbracoV8 it used Blob storage for media storage, BUT the cached items (crops) were hosted in the local storage of the App Service instead.
With Umbraco V10 both media and cache are stored in blob storage.
The website has many media items, here the numbers: 47.3k items in media folder 87.6k items in cache folder
Does anyone have experience with websites that have such a big media storage on azure? Any performance issues?
Joao,
Just wondering if you had found the reason for this outside of this community post as I think I might be seeing a similar scenario.
Thanks, Stuart
No reason and no solution found so far. We now configured the website to use local storage for crops cache and use blob storage only for media storage. But media requests are still very slow some times. The next thing we'll try is to delete unused medias to clean up the blob storage, maybe with less items it will get faster
i have the same issue too
Hi,
Is there a solution for this issue already?
We ran into the same problem.
Grtz Sander
Hi,
After moving from Umbraco 8 to 10+ on multiple projects we are experience similar issues.
Does not matter if the cache is on local or blob storage.
We are seeing at random images taking from 1sec to 40sec to load.
If we disable the blob storage package and use everything by default locally the issue goes away.
This is having a major performance issues on many projects.
Hi,
We are experiencing the same issues. Does someone has a fix or workaround for this after all this time?
Did you hear anything back? I'm getting the same problem.
I have used a CDN to load the image, but I haven't yet checked how much time it takes. I will look into it and get back to you.
No, i didn't get any response. We've found out that the issue is most likely caused by the Umbraco.StorageProviders.AzureBlob package since it is using IFileProvider and this doesn't allow for async calls. And this might cause waiting requests if you get to many at once.
Ronald made a draft PR some time ago for this: https://github.com/umbraco/Umbraco.StorageProviders/pull/26
And some more info i found about this: https://procodeguide.com/asp-net-core/scale-aspnet-core-application-thread/
Its not pretty, but for now what seems to help our website is to increase the minimal allowed threads in de program.cs:
is working on a reply...