[Home]

Summary:ASTERISK-29006: Asterisk 16 on Centos 7 with 16 CPUs and 64 GB RAM cannot process 5CPS
Reporter:Air (Air2020)Labels:
Date Opened:2020-07-22 19:59:37Date Closed:2020-08-06 12:00:01
Priority:MajorRegression?No
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:16.11.1 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Centos 7.8 server with 16 CPUs and 64 GB RAMAttachments:( 0) asterisk_gdb_07222020.log
Description:When VoIP traffic reaches 5 calls per second with 400 concurrent calls the SIP sessions are starting to timeout and eventually no response is being sent from Asterisk to a caller.
Comments:By: Asterisk Team (asteriskteam) 2020-07-22 19:59:38.149-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

By: Air (Air2020) 2020-07-22 20:03:09.654-0500

The GDB traceback is attached.

By: Joshua C. Colp (jcolp) 2020-07-23 04:26:23.515-0500

Disable the DEBUG_THREADS Compiler Flag when building Asterisk. This will drastically reduce performance and should only be enabled when debugging deadlocks.

By: Asterisk Team (asteriskteam) 2020-08-06 12:00:00.825-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines