[asterisk-bugs] [JIRA] (ASTERISK-29814) Very High CPU uses only 80 con-currents calls on asterisk via AMI

[Amardeep (JIRA)]

Amardeep created ASTERISK-29814:
-----------------------------------

             Summary: Very High CPU uses only 80 con-currents calls on asterisk via AMI
                 Key: ASTERISK-29814
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29814
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Applications/app_dial, Applications/app_macro, Applications/app_playback, Channels/chan_pjsip, Channels/chan_sip/General, Codecs/codec_alaw
    Affects Versions: 18.9.0, 18.6.0, 17.0.0, 16.24.0
         Environment: CentOS 7
            Reporter: Amardeep
            Severity: Major


CentOS 7, 40 Core CPU very high Very high CPU use on in 80  calls via ami

We are using clean Asterisk 18.9.0 on Cent OS 7.
TWO SIP trunk connected 
Telecom Provider 
1. TATA : 60 Channels
2. VODAFONE : 90 Channels
audio codec uses : alaw & ulaw for both

server configuration 
Manufacturer: HPE
Product Name: ProLiant DL380 Gen10
Family: ProLiant

RAM : 64 GB 

CPU Info
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                40
On-line CPU(s) list:   0-39
Thread(s) per core:    2
Core(s) per socket:    10
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 85
Model name:            Intel(R) Xeon(R) Silver 4210R CPU @ 2.40GHz
Stepping:              7
CPU MHz:               999.902
CPU max MHz:           3200.0000
CPU min MHz:           1000.0000
BogoMIPS:              4800.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              1024K
L3 cache:              14080K
NUMA node0 CPU(s):     0-9,20-29
NUMA node1 CPU(s):     10-19,30-39

uname -a
Linux localhost.localdomain 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

when CPU load reach around 35 in TOP command most of calls voice issue.
our call flow is very simple
ami originate call from another server --- asterisk dial number--- play audio file--- google API audio to text---- and play another audio based on response.
 




--
This message was sent by Atlassian JIRA
(v6.2#6252)