openstack/neutron
Code Issues Proposed changes

burst should be set near max-rate

Browse Source 
Burst value for TCP traffic should be set as 80% of desired bandwidth
limit value. For example, if the bandwidth limit is set to 1000kbps
then enough burst value will be 800kbit. If the configured burst value
is too low, achieved bandwidth limit will be lower than expected.
If the configured burst value is too high, too few packets could
be limited and achieved bandwidth limit would be higher than expected.

So we should recommend a correct example in case that user ignores
the note.

Change-Id: Iefea3ce699c39e217e89dec93a8fe8ea1a90ac82
This commit is contained in:
Zachary 2017-12-02 16:28:00 +08:00
parent a725e200ac
commit f2d449d486
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/admin/config-qos.rst
View File

@ -223,13 +223,13 @@ First, create a QoS policy and its bandwidth limit rule:
$ openstack network qos rule create --type bandwidth-limit --max-kbps 3000 \
--max-burst-kbits 300 --egress bw-limiter
--max-burst-kbits 2400 --egress bw-limiter
+----------------+--------------------------------------+
| Field | Value |
+----------------+--------------------------------------+
| direction | egress |
| id | 92ceb52f-170f-49d0-9528-976e2fee2d6f |
| max_burst_kbps | 300 |
| max_burst_kbps | 2400 |
| max_kbps | 3000 |
| name | None |
| project_id | |
@ -398,7 +398,7 @@ attached port.
.. code-block:: console
$ openstack network qos rule set --max-kbps 2000 --max-burst-kbits 200 \
$ openstack network qos rule set --max-kbps 2000 --max-burst-kbits 1600 \
--ingress bw-limiter 92ceb52f-170f-49d0-9528-976e2fee2d6f
$ openstack network qos rule show \
@ -408,7 +408,7 @@ attached port.
+----------------+--------------------------------------+
| direction | ingress |
| id | 92ceb52f-170f-49d0-9528-976e2fee2d6f |
| max_burst_kbps | 200 |
| max_burst_kbps | 1600 |
| max_kbps | 2000 |
| name | None |
| project_id | |