Ryan Barrett
Ryan Barrett
A fun bit here will be figuring out how to implement eg [leaky bucket](https://en.wikipedia.org/wiki/Leaky_bucket) on memcache, where we have a limited set of operations. And also where the result isn't...
...or we do it probabilistically! https://blog.cloudflare.com/sometimes-i-cache was great recent read on this.
I'm going to do this as part of the fix for #2089. That means I need to spread out receive tasks deterministically, always, so I'm not going to do leaky...
Shipped this ^, it's working! Probably need to tweak delay monitoring calculation a bit, but we've gone from steady state of receive task queue at roughly zero to many thousand....
Love seeing these shapes. Spikes of enqueued receive tasks, processed gradually over time, no visible corresponding spikes in task run rate.
Thanks for filing! Good idea to track this and start the conversation. Mastodon's quote post design is pretty complicated and heavy, so it hasn't been a high priority for me...
Thanks for all the sleuthing, @jfietkau! #1098 also has a bit more related background on reply controls.
Thanks all, great ideas and info, this is very helpful and useful!
@jfietkau very welcome here! Thanks for the updates.
Fascinating! Thanks for the writeup @jfietkau!