Re:How Gas app cut its Redis Engine CPU Utilization by 80%
by mdeeks on Friday October 21, 2022 @06:22PM
(#33293620)
I think the entire point of this post is just to share a war story and help others understand some Redis problems and debugging steps. It isn't some deeper optimization guide or anything. This exact problem is something I have caused and encountered multiple times in my career now. On my first day at Instacart the entire site was down in an extended outage due to a hot key issue exactly like this. I think stories like this are worth sharing with the community even if it seems trivial to yourself.
Re:How Gas app cut its Redis Engine CPU Utilization by 80%
by aloukissas on Saturday October 22, 2022 @09:40AM
(#33298216)
This is team of 2 engineers that's building + shipping faster than most teams I've seen while having insane number DAUs. Moving fast (and patching problems even faster) is the name of the game here and these guys delivered.
They patched out a gross inefficiency that they created
That said, the diagnostics exhibited here are the exact things I'd do, as a person who visits Redis once maybe every two years.
They're not exactly groundbreaking, and I was hoping to find revelations here; not basics.
You'd hope that code reviews would catch this kind of thing, especially on a small team.