Our Umbraco runs in an auto-scaling cloud in AWS. When load goes up, or if there is a problem with one of the nodes, a new one spins up.
This works well - except that each Umbraco instance takes over 30 minutes to start up. With such long response times, auto scaling does not really work.
Here's what the log file looks like:
2016-11-04 13:05:38,138 [P1096/D2/T1] INFO Umbraco.Core.CoreBootManager - Umbraco 7.5.4 application starting on WEB1
...
2016-11-04 13:06:03,825 [P1096/D2/T1] INFO Umbraco.Core.DatabaseContext - CanConnect = True
2016-11-04 13:34:27,351 [P1096/D2/T1] INFO Umbraco.Core.DatabaseContext - CanConnect = True
...
2016-11-04 13:36:03,585 [P1096/D2/T30] INFO umbraco.content - Save Xml to file...
You can see that there is a 30 minute gap between the two "DatabaseContext - CanConnect = True" entries. What's that about? How can I speed it up? The servers have 8 cores and 30GB ram.
I have the same issue on my Intel i5 16GB desktop. How can I speed up startup?
Umbraco takes over 30 min to start up
Our Umbraco runs in an auto-scaling cloud in AWS. When load goes up, or if there is a problem with one of the nodes, a new one spins up.
This works well - except that each Umbraco instance takes over 30 minutes to start up. With such long response times, auto scaling does not really work.
Here's what the log file looks like:
You can see that there is a 30 minute gap between the two "DatabaseContext - CanConnect = True" entries. What's that about? How can I speed it up? The servers have 8 cores and 30GB ram.
I have the same issue on my Intel i5 16GB desktop. How can I speed up startup?
Hi David,
We have seen similar issues on Azure using Auto scaling. In our case it was building examine indexes for the new instance being the issue.
Dave
+1 for what Dave says - Try boot with Examine index rebuilding disabled by setting RebuildOnAppStart to False
e.g.
See: https://our.umbraco.org/documentation/reference/config/examinesettings/
If you use Examine and this does turn out to be the issue - then you'll need a strategy to share indexes across instances.
How much content do you have out of interest?
40,000 documents, 2.2GB.
Looks like RebuildOnAppStart worked, and content is still replicating.
Hi David,
What is the startup time like now?
About two minutes.
is working on a reply...