diff options
| author | wojtekt <wojtekt@google.com> | 2019-07-31 16:17:09 +0200 |
|---|---|---|
| committer | wojtekt <wojtekt@google.com> | 2019-07-31 16:17:09 +0200 |
| commit | e3b31ac693e14c1883bbc7f58c0a4d902502a1e0 (patch) | |
| tree | 5a93e39d81bda5a9e458edc1a432ac4637bb7b6d /sig-scalability | |
| parent | 8d302b7bf09602a53009e95cf44e944f05a6eb38 (diff) | |
Link thresholds
Diffstat (limited to 'sig-scalability')
| -rw-r--r-- | sig-scalability/slos/api_call_latency.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/sig-scalability/slos/api_call_latency.md b/sig-scalability/slos/api_call_latency.md index 69af0f13..7e6b0785 100644 --- a/sig-scalability/slos/api_call_latency.md +++ b/sig-scalability/slos/api_call_latency.md @@ -50,6 +50,11 @@ the amount of work to do (which is number of objects of a given type in a given scope) plus some constant overhead. For better tracking of performance, we may want to define purely internal SLI of "latency per object". But that isn't in near term plans. +- To recall, SLOs are guaranteed only if thresholds defined in [thresholds file][] +are satisfied. This is particularly important for this SLO, because it limits +the number of objects that are returned by LIST calls. + +[thresholds file]: https://github.com/kubernetes/community/blob/master/sig-scalability/configs-and-limits/thresholds.md ### Caveats - The SLO has to be satisfied independently from used encoding in user-originated |