4 Jul
2020
4 Jul
'20
3:01 p.m.
Thinking a bit longer about this, this behaviour is perfectly reasonable in the "serverless" model; resources (both CPU and memory) are throttled down to 0 when the service is not processing requests, which is exactly what ekg picks up. Why logs are printed out even outside of requests is still a bit of a mystery, though ..
I'm very puzzled by this: both rts.gc.current_bytes_used and rts.gc.max_bytes_used gauges return constant 0 in the case of Service 2 (the Cloud Run one), even though I'm using the same sampling/logging functionality and build options for both services.