How can I find out what is causing poor performance in a load balanced azure environment?
We have a umbraco 9.4.3 site running on azure appservice with kubernetes. There is one back-end server, one sql server and two fronts. A CDN minimizes the traffic to to the fronts.
Media-files, logs and everything from the TEMP-folder are stored on a common file share.
Our problem is that back-office performance is very poor - deleting/moving a node with a few pages or trying to empty the recycle bin takes minutes or leads to sql server timeout errors:
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
---> System.ComponentModel.Win32Exception (258): Unknown error 258
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
...
Umbraco background jobs (like ContentVersionCleanup) also produce the same type of errors.
MainDomLock is set to SqlMainDomLock and both fronts have write permission to the database.
We have dev and test-enviroments (not load balanced) with the same number of pages and they are fast and work like a normal umbraco site does.
We are about to upgrade from 9->10 and then from 10->13 but I am hesitant since I believe that the migration scripts might time out (as so many other sql commands do) leading to a failed upgrade.
My main question is - how can we find what is causing this poor behavior?
How can I find out what is causing poor performance in a load balanced azure environment?
We have a umbraco 9.4.3 site running on azure appservice with kubernetes. There is one back-end server, one sql server and two fronts. A CDN minimizes the traffic to to the fronts. Media-files, logs and everything from the TEMP-folder are stored on a common file share.
Our problem is that back-office performance is very poor - deleting/moving a node with a few pages or trying to empty the recycle bin takes minutes or leads to sql server timeout errors:
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. ---> System.ComponentModel.Win32Exception (258): Unknown error 258 at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) ...
Umbraco background jobs (like ContentVersionCleanup) also produce the same type of errors.
MainDomLock is set to SqlMainDomLock and both fronts have write permission to the database.
We have dev and test-enviroments (not load balanced) with the same number of pages and they are fast and work like a normal umbraco site does.
We are about to upgrade from 9->10 and then from 10->13 but I am hesitant since I believe that the migration scripts might time out (as so many other sql commands do) leading to a failed upgrade.
My main question is - how can we find what is causing this poor behavior?
Thankful for any suggestions, cheers!
is working on a reply...