When implementing deficit weighted round robin queuing, what importance does the weight value have?
When implementing deficit weighted round robin queuing, what importance does the weight value have?
In deficit weighted round robin (DWRR) queuing, the weight value represents the percentage of interface bandwidth that is allocated to each queue. The weight determines how much bandwidth a queue can use relative to other queues, ensuring that each queue receives a predictable share of the available bandwidth based on its weight.
Assigns the deficit weighted round robin (DWRR) algorithm and its weight to a queue in a schedule profile. DWRR allocates available bandwidth among all non-empty queues in relation to the queue weights. The no form of this command removes the DWRR algorithm from a queue in a schedule profile.
"Using weights that add up to 100 makes it easy to estimate the bandwidth: the weight converts to a percentage of the bandwidth" HPE Press Study Guide, Page 385
D DWRR allocates available bandwidth among all non-empty queues in relation to the queue weights.
Page 853 Study Guide
D is correct : From ACSP learning book Quality of Service (QoS) : "DWRR & WFQ ... in both algorithms, each queue receives a predictable share of the bandwidth based on the queue's relative priority, or weight. You can calculate the queue's bandwidth by taking the queue weight and dividing it by the total weight of all non-empty queues and then multiplying that by the port bandwidth"