diff options
| author | Mark Michelson <mmichelson@digium.com> | 2015-11-13 14:19:35 -0600 |
|---|---|---|
| committer | Mark Michelson <mmichelson@digium.com> | 2015-11-13 14:19:35 -0600 |
| commit | e8881e177046422690d2e87417a93b253469c379 (patch) | |
| tree | d3aab1a43860805cbbe670c516d7f7a05391e0f2 /res/res_pjsip_xpidf_body_generator.c | |
| parent | 40b58a5d2b2acddc8ff616b4c0fbdc808e16a9da (diff) | |
Taskprocessors: Increase high-water mark
In practical tests, we have seen certain taskprocessors, specifically
Stasis subscription taskprocessors, cross the recently-added high-water
mark and emit a warning. This high-water mark warning is only intended
to be emitted when things have tanked on the system and things are
heading south quickly. In the practical tests, the Stasis taskprocessors
sometimes had a max depth of 180 tasks in them, and Asterisk wasn't in
any danger at all.
As such, this ups the high-water mark to 500 tasks instead. It also
redefines the SIP threadpool request denial number to be a multiple of
the taskprocessor high-water mark.
Change-Id: Ic8d3e9497452fecd768ac427bb6f58aa616eebce
Diffstat (limited to 'res/res_pjsip_xpidf_body_generator.c')
0 files changed, 0 insertions, 0 deletions