UserSummary on every comment used to cost 3 SQL round-trips. We cache it in Valkey for 45s keyed by user:{id}:summary.
The failure mode is a display-name change that stays stale in a long thread. Mods noticed first.
We now bust that key on profile PUT. Still debating a 5s in-process L1 in Axum. Worth the split-brain?
Staff view: please do not delete the thread if this is a duplicate. Link the canonical Issue instead.
Posted a Guide recap of this thread so we are not asking people to mine comments.
We hit the same wall on caching. Replica lag was the surprise, not CPU.
For campus we used entity_type=course and left the template as Question. Search Console looks sane.
Thanks — leaving this up for the next team that searches the same string.
UserSummary on every comment used to cost 3 SQL round-trips. We cache it in Valkey for 45s keyed by user:{id}:summary.
The failure mode is a display-name change that stays stale in a long thread. Mods noticed first.
We now bust that key on profile PUT. Still debating a 5s in-process L1 in Axum. Worth the split-brain?
Posted a Guide recap of this thread so we are not asking people to mine comments.
We hit the same wall on caching. Replica lag was the surprise, not CPU.
For campus we used entity_type=course and left the template as Question. Search Console looks sane.
Thanks — leaving this up for the next team that searches the same string.
Sign in or create an account to share your thoughts, solutions, or feedback.
Staff view: please do not delete the thread if this is a duplicate. Link the canonical Issue instead.