Example: Configuring Wred And Dynamic Queue Thresholds; Figure 6: Defining Different Drop Behavior For Each Queue - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual

Figure 6: Defining Different Drop Behavior for Each Queue

Related
Documentation

Example: Configuring WRED and Dynamic Queue Thresholds

Copyright © 2010, Juniper Networks, Inc.
that classifies packets into one of four traffic classes. Each traffic class has a different
queueing behavior, drop treatment, and scheduler treatment.
Configuring WRED on page 30
Dropping Behavior Overview on page 25
RED and WRED Overview on page 26
RED typically operates on fixed-size queues, and you can configure the router to use
fixed-size queues. However, by default, the router employs dynamic queue thresholds
to provide a good balance between sharing the egress buffer memory between queues
and protecting an individual queue's claim on its fair share of the egress memory.
Fixed-size queues become problematic as the number of configured queues scales into
the thousands, because allocating disjointed partitions of buffer memory to each queue
means the allocations become quite small, and most likely not all queues are
simultaneously active.
In general, you use queues as follows:
Fixed-size queues on core routers and core-facing interfaces where the number of
queues is relatively small (tens or hundreds, but not thousands).
Chapter 4: Configuring Dropping Behavior with RED and WRED
33