Configuring target burst capacity

Target burst capacity is a global and per-revision integer setting that determines the size of traffic burst a Knative application can handle without buffering.

If a traffic burst is too large for the application to handle, the Activator service will be placed in the request path to protect the revision and optimize request load balancing.

The Activator service is responsible for receiving and buffering requests for inactive revisions, or for revisions where a traffic burst is larger than the limits of what can be handled without buffering for that revision.

Target burst capacity can be configured using a combination of the following parameters:

• Setting the targeted concurrency limits for the revision. For more information, see the documentation on concurrency.
• Setting the target utilization parameters. For more information, see the documentation on target utilization.
• Setting the target burst capacity.

Setting the target burst capacity

• Global key: target-burst-capacity
• Per-revision annotation key: autoscaling.knative.dev/targetBurstCapacity
• Possible values: float (0 means the Activator is only in path when scaled to 0, -1 means the Activator is always in path)
• Default: 200

Note: If the activator is in the routing path, it will fully load all replicas up to containerConcurrency. It currently applies target utilization only on revision level.

Example:

• Per Revision
• Global (ConfigMap)
• Global (Operator)

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  annotations:
  name: s3
  namespace: default
spec:
  template:
    metadata:
      annotations:
        autoscaling.knative.dev/targetBurstCapacity: "70"

apiVersion: v1
kind: ConfigMap
metadata:
  name: config-autoscaler
  namespace: knative-serving
data:
  target-burst-capacity: "70"

apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
  name: knative-serving
spec:
  config:
    autoscaler:
      target-burst-capacity: "70"