Divya Rani (ad0bbb47) at 17 Mar 17:09

Divya Rani (fc83b905) at 17 Mar 16:39

I like the idea of exposing a Gitaly pressure metric to (internal) clients as a means of encouraging them to throttle requests. Would the Gitaly team be responsible for implementing the client-side code too?

I have proposed this idea to the production engineering team, and if they align, I'm thinking we can own the implementation end-to-end.

Yeah, it does make sense to link this document.

I have added the x-score documentation - https://developers.cloudflare.com/waf/rate-limiting-rules/request-rate/#example-c and for more info, here is the in-depth discussion regarding the headers - https://gitlab.com/groups/gitlab-com/gl-infra/-/work_items/2003#note_3153776857

No, it doesn't. I have rephrased the sentence.

Divya Rani (0c4c322d) at 17 Mar 16:10

Divya Rani (2db66f96) at 17 Mar 16:07

@gl-gitaly As Gitaly has several concurrent efforts to improve how it manages resources under load, I have created this doc to outline how they compose into a cohesive system. While I'm still iterating on the doc, specifically on sending pressure signals to Rails, I would appreciate any feedback.

Divya Rani (a699c5e7) at 16 Mar 16:06

Divya Rani (9cc09413) at 16 Mar 15:49

Divya Rani (6aab9ee8) at 16 Mar 15:45

Divya Rani (89efe37e) at 16 Mar 15:43

This MR attempts to outline how LoadMonitor, BurdenTracker, rate limiter, and other components compose into a layered system for load management and DoS mitigation.

Closes #7108

Divya Rani (dd32f938) at 16 Mar 14:12

Divya Rani (61f332d9) at 16 Mar 09:16

Divya Rani (6b8102f0) at 16 Mar 09:16

... and 1 more commit