I currently work with a website running Umbraco v8.8.0, and am attempting to sort 116 content items. When I run the sort, I am getting a message of, "Failed to sort content." The site is running on a S1 Azure SQL database, and a S2 Azure App Service plan. The site runs behind Cloudflare, and is cached at least 80% of the time.
I'm looking for any advice on whether I need to upgrade the Azure SQL database plan to S2, or if there is something else I can do to ensure the sorting is saved properly. At roughly 75 content items, the sorting was working fine (I did not measure between the 75 and current 116, as the client entered all content after the first).
I'm actually not getting anything in the logs due to this issue. I get an error stating to have the administrator check the logs, but the file only has a single warning for excessive headers (using Cloudflare which sets the Server header).
If I bring down a copy of the website to my local machine, the sorting is done quickly and properly (although my available RAM and CPU is obviously much higher).
I haven't had a chance to dig into the Umbraco 8 source code yet, but I'm wondering if the full entity is being retrieved from the database, and then being updated. Maybe there is a limit for an IN clause, where another strategy is used once a certain number of items is reached.
Well if its working fine locally, def sounds like a possible infrastructure issue. I don't have a lot of experience with umbraco on azure, but we have various sites with hundreds of nodes that we sort without issue on relatively simple shared hosting environments.
Sorting Timed Out
I currently work with a website running Umbraco v8.8.0, and am attempting to sort 116 content items. When I run the sort, I am getting a message of, "Failed to sort content." The site is running on a S1 Azure SQL database, and a S2 Azure App Service plan. The site runs behind Cloudflare, and is cached at least 80% of the time.
I'm looking for any advice on whether I need to upgrade the Azure SQL database plan to S2, or if there is something else I can do to ensure the sorting is saved properly. At roughly 75 content items, the sorting was working fine (I did not measure between the 75 and current 116, as the client entered all content after the first).
My first thought is, that's not a ton of content, any more detailed info on the errors in the logs?
I'm actually not getting anything in the logs due to this issue. I get an error stating to have the administrator check the logs, but the file only has a single warning for excessive headers (using Cloudflare which sets the Server header).
If I bring down a copy of the website to my local machine, the sorting is done quickly and properly (although my available RAM and CPU is obviously much higher).
I haven't had a chance to dig into the Umbraco 8 source code yet, but I'm wondering if the full entity is being retrieved from the database, and then being updated. Maybe there is a limit for an IN clause, where another strategy is used once a certain number of items is reached.
Well if its working fine locally, def sounds like a possible infrastructure issue. I don't have a lot of experience with umbraco on azure, but we have various sites with hundreds of nodes that we sort without issue on relatively simple shared hosting environments.
is working on a reply...