You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Не совсем понимаю, что лучше написать и куда, чтобы это было полезно.
Наш `use-case` заключается в том, что мы теперь сможем получать сигнал о том, что работает `congestion control`, и использовать его для того, чтобы ограничивать не весь трафик, а трафик, размеченный по тирам
commit_hash:47603ad00e5c8cec52a944850c4be886716fc443
Copy file name to clipboardExpand all lines: scripts/docs/en/userver/congestion_control.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,8 @@ CC can run in `fake-mode` with no RPS limit (but FSM works). CC goes into `fake-
12
12
* there are no reliable guarantees on CPU, in this case RPS-limit would be triggered too often,
13
13
* service has no HTTP-handles others than server::handlers::Ping.
14
14
15
+
`fake-mode` can be useful for more flexible traffic restriction settings, according to it's more complex logic, which can be implemented in a middleware.
16
+
15
17
## Usage
16
18
17
19
congestion_control::Component can be useful if your service stops handling requests when overloaded, significantly increasing response time, responding with HTTP 500 codes to requests, eating memory.
0 commit comments