Hi Rashidov Abdumajid, Cloud Run provides metrics related to memory and network usage. based on that you should be able to find out what is the root cause of the issue. https://cloud.google.com/monitoring/api/metrics_gcp_p_z#gcp-run
Best regards, Andrzej G. środa, 13 sierpnia 2025 o 16:58:00 UTC+2 Rashidov Abdumajid napisał(a): > Hey everyone, > > We're running a gRPC service on Cloud Run and keep hitting this error > after a few minutes under load: Error: 8 RESOURCE_EXHAUSTED: Bandwidth > exhausted or memory limit exceeded > Our setup: > > - 50 requests per second > - Each request takes 3-6 seconds to respond > - Memory: 512 MiB > - CPU: 1 > - Max concurrency: 20 per instance > - Max instances: 100 > > The service works fine for short bursts, but once we hit sustained traffic > for a few minutes, multiple instances start throwing this error. > > I found that Cloud Run has a 600 Mbps bandwidth limit per instance. Our > gRPC responses might be pretty large, so I'm thinking we're hitting that > limit. > Questions: > > 1. Is this definitely a bandwidth issue, or could it be something else? > 2. Should we lower the concurrency to spread traffic across more > instances? > 3. Will bumping up memory/CPU help with bandwidth, or are those limits > fixed? > 4. Any other config changes we should try? > > We're a bit stuck here - the service works great until it hits this wall. > Any advice would be awesome! > > Thanks! > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/grpc-io/877df816-41a0-427e-8544-0e5761503747n%40googlegroups.com.
