Configuring target burst capacity

    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.

    • Setting the targeted concurrency limits for the revision. For more information, see the documentation on concurrency.
    • Setting the target burst capacity.
    • Global key:
    • Per-revision annotation key: autoscaling.knative.dev/targetBurstCapacity
    • Default:

    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:

    Feedback

    Glad to hear it! Please tell us how we can improve.

    Sorry to hear that. Please .