Update recommended shaper settings
Bug #1941653 reported by
Galen Charlton
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenSRF |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
Currently the OpenSRF installation instructions recommend increasing the ejabberd traffic shaper rates from their default values. I propose that we instead change the recommendation to have ejabberd _not_ set a shaper rate, i.e., set
s2s_shaper: none
c2s_shaper: none
This would stop ejabberd from imposing any bandwidth limit. Doing this would reduce request latency by large Evergreen systems, as there's generally no reason to have an in-flight request sit in an ejabberd queue just to meet an arbitrarily-set bandwidth limit. Rate-limiting requests sent to Evergreen would be better done on the edge.
OpenSRF master
| tags: | added: documentation installation performance |
| Changed in opensrf: | |
| importance: | Undecided → Medium |
Revision history for this message
| Jason Stephenson (jstephenson) wrote | #1 |
| Changed in opensrf: | |
| status: | New → Confirmed |
To post a comment you must log in.
I found that the following configuration also works:
shaper: {}
shaper_rules: {}
However, Galen's suggestion makes fewer changes to the default configurations.