u/DangerousBug5998

I’ve been using Azure App Service slots for a long time to avoid cold starts during deployment. My typical process involves deploying to a staging slot (which is already running), testing to ensure it's running properly, and then swapping with the production slot when I'm ready. This setup has allowed me to achieve zero-downtime deployments.

However, recently I’ve noticed that after the swap, I’m experiencing cold starts of around 30 to 35 seconds, which is something new. Has anyone else encountered this issue? Is there anything else I can do to avoid cold starts?

I also added to the app settings in Azure

WEBSITE_SWAP_WARMUP_PING_PATH=/api/health
WEBSITE_SWAP_WARMUP_PING_STATUSES=200-299

I’ve been using Azure App Service slots for a long time to avoid cold starts during deployment. My typical process involves deploying to a staging slot (which is already running), testing to ensure it's running properly, and then swapping with the production slot when I'm ready. This setup has allowed me to achieve zero-downtime deployments.

However, recently I’ve noticed that after the swap, I’m experiencing cold starts of around 30 to 35 seconds, which is something new. Has anyone else encountered this issue? Is there anything else I can do to avoid cold starts?

In case you're wondering why I do the swap manually, cause i had 1 too many times a 500.30 😄