Replit Deployments: Cold start latency in Wake-on-Request environments

Production Runtime Behavior

Replit Deployments utilize containerization to separate the production runtime from the interactive development shell. For server-side applications, the platform offers different hosting states, including a 'Wake-on-Request' configuration designed to optimize resource usage when traffic is low.

Resource State Transition

When an application is hosted under a plan that supports Wake-on-Request, the container may enter a dormant state. This introduces a transition period when the first request arrives after a period of inactivity, potentially impacting the initial response time compared to 'Always On' deployments.

Given the differences between the interactive development environment and the production deployment pipeline, it is unclear how these cold starts affect specific runtime overheads.

• What is the typical latency range for a container to transition from dormant to active in a Wake-on-Request deployment?
• Are there specific configuration triggers within the deployment settings to minimize this latency without upgrading to an Always On plan?