I'm on UAAS. We have roughly 700 contentXml items. We are seeing the following entries in our log files and the site becomes unresponsive when publishing new content.
22:30:56.020 INFO umbraco.content
Saved Xml to file.
22:30:31.497 INFO umbraco.content
Save Xml to file...
Note the timestamp is ~25 seconds to regenerate the XMLCache
Should it realistically take the site offline for that amount of time? What happens when we get above 2000 articles? Is this purely processor, memory, hdd write time going on here?
It looks like something is wrong with your installation, we just tested on similar site and republish takes few seconds, do you have some event handlers on save?
Hi.
We are using Umbraco Cloud so AQL azure 2016. We ended up just disabling the umbraco.config file completely by adding the following setting in umbracoSettings. You can see the result difference here.
We have custom content event handling but it processes this stuff in <100 ms on our local machines. We have also tested with local .sqlExpress, Compact CE and regular SQL server. The only times it starts blowing up is on Azure App Service and the time to save is different on each machine.
Saving XML to cache takes a very long time
I'm on UAAS. We have roughly 700 contentXml items. We are seeing the following entries in our log files and the site becomes unresponsive when publishing new content.
Note the timestamp is ~25 seconds to regenerate the XMLCache
Should it realistically take the site offline for that amount of time? What happens when we get above 2000 articles? Is this purely processor, memory, hdd write time going on here?
Hi Mac,
It looks like something is wrong with your installation, we just tested on similar site and republish takes few seconds, do you have some event handlers on save?
Thanks,
Alex
What database are you using?
Hi. We are using Umbraco Cloud so AQL azure 2016. We ended up just disabling the umbraco.config file completely by adding the following setting in umbracoSettings. You can see the result difference here. We have custom content event handling but it processes this stuff in <100 ms on our local machines. We have also tested with local .sqlExpress, Compact CE and regular SQL server. The only times it starts blowing up is on Azure App Service and the time to save is different on each machine.
Hi Mac,
I would say that difference is really big. Thanks for sharing, great example.
Thanks,
Alex
is working on a reply...