From 4048921b916784888e0b64ef55712f6f80d5bd58 Mon Sep 17 00:00:00 2001 From: Paul Schweigert Date: Tue, 11 Oct 2022 12:26:50 -0400 Subject: [PATCH] Add info on relation between KPA mode and window (#5269) * add info on relation between KPA mode and window Signed-off-by: Paul S. Schweigert * Update docs/serving/autoscaling/kpa-specific.md Signed-off-by: Paul S. Schweigert Co-authored-by: Ashleigh Brennan --- docs/serving/autoscaling/kpa-specific.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/serving/autoscaling/kpa-specific.md b/docs/serving/autoscaling/kpa-specific.md index 477937030..c943bbc03 100644 --- a/docs/serving/autoscaling/kpa-specific.md +++ b/docs/serving/autoscaling/kpa-specific.md @@ -9,7 +9,7 @@ The KPA acts on [metrics](autoscaling-metrics.md) (`concurrency` or `rps`) aggre These windows define the amount of historical data that the Autoscaler takes into account, and are used to smooth the data over the specified amount of time. The shorter these windows are, the more quickly the Autoscaler will react. -The KPA's implementation has two modes: **stable** and **panic**. +The KPA's implementation has two modes: **stable** and **panic**. There are separate aggregate windows for each mode: `stable-window` and `panic-window`, respectively. Stable mode is used for general operation, while panic mode by default has a much shorter window, and will be used to quickly scale a revision up if a burst of traffic arrives.