I’m deploying a gRPC service to Cloud Run and this service establishes bi-directional stream with the client and should be long-lived. I see that unless I choose to always allocate my instances, Cloud Run’s pricing model is based on requests. A part of that calculation seems to be the execution time per request. I’m looked for this but it’s not clear to me whether if a long-lived gRPC stream is considered a running execution. That is, am I being charged for a long lived gRPC stream across the entire duration of that stream? Or is the stream transparent to GCP and I’m only charged per message sent inside the stream?