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
Copy file name to clipboardExpand all lines: pkg/epp/framework/plugins/flowcontrol/usagelimits/priorityholdback/README.md
+17-7Lines changed: 17 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,21 +12,29 @@ Each active priority level receives an admission ceiling in [0.0, 1.0]. During e
12
12
13
13
Higher-priority traffic continues to flow until saturation reaches its own (higher) ceiling, providing quality-of-service differentiation under load.
14
14
15
-
## Strategies
15
+
## Configuration
16
16
17
-
Two strategies are available for computing per-priority ceilings. Both produce `maxCeiling` for the highest priority and`minCeiling` for the lowest.
17
+
Behavior is configured via two independent parameters: `shape` and `domain`. The resulting ceilings always range from `maxCeiling` for the highest priority to`minCeiling` for the lowest.
18
18
19
-
### `stepwise-spread`
19
+
### `shape`
20
20
21
-
Distributes ceilings in equal steps by rank, ignoring numerical priority values.
21
+
The interpolation curve used to distribute ceilings across the range. Currently only `"linear"` is supported.
22
+
23
+
### `domain`
24
+
25
+
How priority levels are mapped to positions in the ceiling range.
26
+
27
+
#### `rank` (default)
28
+
29
+
Distributes ceilings in equal steps by ordinal rank, ignoring numerical priority values. Ceilings are evenly spaced across `[minCeiling, maxCeiling]`.
0 commit comments