Hacker News Reader

Thanks for offering. In the graph labeled "Prod customer throughput: (higher is better)" eyeballing it within a week you are seeing ~2k qps peak increase over the previous week.

Operationally, how do you handle landing that large of a perf improvement? If my data store changed that much in a week it could break something.

View on HN

Generally the more throughput the system supports the better. In this case we were hitting limits (btw each operation is many queries of different sizes) and the customer observed higher latencies which is typical if the system can't sustain the throughput required.

After this change latencies are back to normal and throughput increased.

Ahh, so it was a customer pain point of higher latency so they were happy to see latency go down and throughput go up. Good to hear.

Great write up, cheers to the people involved.

Reply on news.ycombinator.com