Cold start, and min_replicas if you run it yourself

If the hosted service has been idle, the first request may take longer while Azure starts the container. If that request times out, try again after a short pause. If the problem continues, check the error message or get help.

If you run the server yourself with deploy/krusgraph.sh, min_replicas in deploy/krusgraph.json decides whether it scales to zero: 0 (the default) scales to zero when idle and is the cheapest, 1 keeps one instance running so idle time does not cause a cold start, at the cost of one always-on instance. A new revision or a restart can still delay a request. The change takes effect with --update. A container on a VM or in Docker does not scale to zero.