Hi Jason - thanks for the reply.
The SQL DB is a Standard S6 - 400DTUs
There are two load balanced web apps (we scale this out in busy times)
HaWebv1020231005091658Plan (P2v3: 2)
I would hope with the Azure costs involved with these that this is ample to startup a website!!
I hate trying to get to the logs of these load balanced sites - I’ll have a better look today but I did a copy with a clone of the DB and a single webapp and it was 4 minutes. It think it’s strongly pointing at an issue in the DB in this scenario (for example releases the site starts relatively quickly in the deployment slot and that’s doing the same thing as a cold start.
There is a lot of custom logic on startup (caching of services that uses Umbraco data) I’m sure I could make improvements but my first task it see what is “normal” - e.g. what is just the Umbraco startup due to the amount of content. Then see what the extra sugar in this project is causing.