A Cloud Run web app shows slow initial page loads (cold starts) for a few hundred users. Follow Google recommendations to mitigate this. What should you do?

Setting the Cloud Run service's minimum instances to 3 directly addresses cold starts by ensuring that a specified number of container instances are always running and ready to serve requests, eliminating the startup delay for the first few requests. This keeps instances "warm." Setting concurrency to 1 would make each instance handle only one request at a time, potentially increasing the number of instances needed but not directly solving cold starts. Setting maximum instances to 100 defines the upper scaling limit but doesn't prevent cold starts for the initial requests. Updating to HTTP/2 might improve network efficiency but doesn't impact the container's startup time.