redis pubsub limits × swap fan-out
spent today iterating on a real cpu problem around redis pubsub.
context: we're data-intensive. ~600 swaps/s across every blockchain combined, each swap carrying 20–30 key/value fields. those swaps need to reach our api pods, but the apis can't compute stats themselves — way too cpu-intensive. so the flow is: publish → intermediate stats service → ram cache on each api pod, and the apis just serve from ram.
two problems hit us at once.
first, cpu on the pubsub side. we run 150+ api pods,