Our user experience that the Umbraco Backoffice gets slower the longer its in use. If the user relog then its back to normal speed.
Can it be memory specific? Or browser specific? Or a third option?
Can i set the allowed memory usage somewhere? Or do anyone have a better idear of whats going on?
The only ERROR OR WARN there is in the log. Is a SEOchecker error getting the media history as shown. (I dont think that what makes it slow..)
ERROR SEOChecker.Events.UrlHistoryEventHandler - SEOChecker: Error getting media history
System.NullReferenceException: Object reference not set to an instance of an object.
at SEOChecker.Events.UrlHistoryEventHandler.(IMedia )
at SEOChecker.Events.UrlHistoryEventHandler.(IMediaService , SaveEventArgs`1 )
After some more testing...
I can now say that a relog do NOT help. And the slow load speed is somehow due to the browsers memory usage. Reopen the browser help, since it clears the memory used.
I hit a similar problem with a large site I was working on, where the "Meta Tags" field, was being powered by a "tags" property type
Turned out to be related to the TEMP Storage , used by the browser, and how the AutoComplete JS works in Umbraco.
I think in Chrome and Firefox the HTML Temp Storage Limit is 5MB (Which can be increased, via the browser config). But this didnt remedy the slowness, it just meant Umbraco could stuff in more data to churn through)
The "Tags" property type, which was stuffing the TEMP storage. The more nodes you viewed, the more data got stuffed in there, to be used by the AutoComplete.
My only solution/option. Was to swap out the "tags" property type (which was being used for metatags), for a textarea field.
Just to be clear.
You are taking about the storage in the Application tab right?
There is only content in Cookies. Where i found UMB_UCONTEXT at a size of 1292B. But when i reopen the browser its still the same size, but normal load speed again.
Umbraco backend load speed gets slower over time
Using Umbraco version 7.5.7.
Our user experience that the Umbraco Backoffice gets slower the longer its in use. If the user relog then its back to normal speed.
Can it be memory specific? Or browser specific? Or a third option?
Can i set the allowed memory usage somewhere? Or do anyone have a better idear of whats going on?
The only ERROR OR WARN there is in the log. Is a SEOchecker error getting the media history as shown. (I dont think that what makes it slow..)
After some more testing... I can now say that a relog do NOT help. And the slow load speed is somehow due to the browsers memory usage. Reopen the browser help, since it clears the memory used.
Can i do anything about that?
I hit a similar problem with a large site I was working on, where the "Meta Tags" field, was being powered by a "tags" property type
Turned out to be related to the TEMP Storage , used by the browser, and how the AutoComplete JS works in Umbraco.
I think in Chrome and Firefox the HTML Temp Storage Limit is 5MB (Which can be increased, via the browser config). But this didnt remedy the slowness, it just meant Umbraco could stuff in more data to churn through)
The "Tags" property type, which was stuffing the TEMP storage. The more nodes you viewed, the more data got stuffed in there, to be used by the AutoComplete.
My only solution/option. Was to swap out the "tags" property type (which was being used for metatags), for a textarea field.
We do not use the Tags Datatype anywhere in our solution.
Do you have any other idear?
Use Chrome Dev tools, and you can drill down on the HTML5 Data storage, and see what it contains, and what's populating it.
That's how I came across the above issue.
I will try and keep an eye out there. Thanks!
Just to be clear. You are taking about the storage in the Application tab right?
There is only content in Cookies. Where i found UMB_UCONTEXT at a size of 1292B. But when i reopen the browser its still the same size, but normal load speed again.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.