The meter read 1.1M commands and 133,421 connections, against 17,000 writes.
The queue cannot produce that: an idle worker asks once every fifteen seconds
and a run publishes a progress line at a time.
It was CrewAI's lock. With REDIS_URL set, CrewAI uses `portalocker.RedisLock` -
a pub/sub lock: `pubsub_numsub`, `client_setname`, `subscribe`, a second
`pubsub_numsub` and an `unsubscribe`, on a pubsub connection opened and closed
around them, with a thread polling every 100ms while it is held. One is taken
per `Crew(...)` built and another per task output stored, and this platform
builds a crew per model call.
What it guards is a SQLite file in the container's own storage directory, so a
distributed lock has nothing to coordinate. The file backend existed but was
installed only when a probe found Redis unreachable - covering the laptop and
never the server. It is installed always now.
Also: the event stream wrapped a `get_message()` that defaults to timeout=0 in
`wait_for(..., 2.0)`…
Group on the column, not on an expression holding a literal (part 2)