John Spray

>If we want to keep such hidden timelines, then we don't really need the proposed merge API, I suppose. We still need it: if someone uses the reset API repeatedly...

This week: - Get the existing PR green for merge.

This week: - Compare old/new on gc_feedback (staircasing) test case. - Fix the edge case where too many deltas on one key can result in oversized layer files. Deferring work...

Status: - bumped last week by walredo latency - will start after io_uring stuff is wrapped.

Initial draft PR is up for review -- could land this week. Testing: - In staging we can enable throttling for everyone? Benchmarks will be unhappy. So we can set...

Status: - Initial code landed on Friday - Next: enable for all tenants in staging, watch for ~2 days and overlap with Peter's bench. - If staging is OK, identify...

This week: - Figure out our plan for making our latency metrics exclude the throttling time, and other metrics to measure impact/activity of throttling (currently just have logs) - Go...

Status: - We alert if a tenant is throttled on >2% of requests - Actions on the alerts: - if a client is a legacy pod that should be migrated...

- Last week: enabled in CI. No major issues. 1-2 flaky tests being investigated to confirm they're pre-existing issues. - This week: benchmarking - This week: enable in staging.

Monitoring staging with new metrics through this week, to get more insight on whether our limits on locked memory are going to be a problem in prod. Maybe prod next...