Hi Razvan, During starting up the opensips service, I see the first opensips child process (pid"11172) consumes CPU process to 70-80% and later drop downs to 0.3 - 0.0 % CPU per core. See below;
[root@qorblpsisprxyd1 ~]# top -c -u opensips top - 10:49:54 up 76 days, 23:31, 5 users, load average: 0.00, 0.00, 0.00 Tasks: 229 total, 1 running, 228 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0%us, 0.1%sy, 0.0%ni, 99.9%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 65964364k total, 2568124k used, 63396240k free, 180220k buffers Swap: 1023996k total, 0k used, 1023996k free, 1226104k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11177 opensips 20 0 165m 5696 4528 S 0.3 0.0 0:00.23 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11187 opensips 20 0 165m 5628 4460 S 0.3 0.0 0:00.41 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11166 opensips 20 0 165m 6892 5752 S 0.0 0.0 0:00.23 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11168 opensips 20 0 165m 1980 840 S 0.0 0.0 0:00.00 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11169 opensips 20 0 165m 1464 328 S 0.0 0.0 0:00.53 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11171 opensips 20 0 165m 1640 504 S 0.0 0.0 0:00.15 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11172 opensips 20 0 166m 40m 38m S 0.0 0.1 0:02.61 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11174 opensips 20 0 165m 6304 5136 S 0.0 0.0 0:00.24 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11175 opensips 20 0 165m 5884 4716 S 0.0 0.0 0:00.22 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11179 opensips 20 0 165m 7660 6492 S 0.0 0.0 0:00.27 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11181 opensips 20 0 165m 7756 6588 S 0.0 0.0 0:00.33 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11183 opensips 20 0 165m 5520 4352 S 0.0 0.0 0:00.34 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11185 opensips 20 0 165m 7336 6168 S 0.0 0.0 0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11189 opensips 20 0 165m 7320 6152 S 0.0 0.0 0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11190 opensips 20 0 165m 4688 3528 S 0.0 0.0 0:00.30 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips [root@qorblpsisprxyd1 ~]# opensipsctl fifo ps Process:: ID=0 PID=11166 Type=attendant Process:: ID=1 PID=11168 Type=MI FIFO Process:: ID=2 PID=11169 Type=time_keeper Process:: ID=3 PID=11171 Type=timer Process:: ID=4 PID=11172 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=5 PID=11174 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=6 PID=11175 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=8 PID=11179 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=10 PID=11183 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=11 PID=11185 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=12 PID=11187 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=13 PID=11189 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=14 PID=11190 Type=Timer handler OpenSIPs used by each CPU processor; [root@qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips PID PSR COMMAND 11166 0 opensips 11168 2 opensips 11169 6 opensips 11171 5 opensips 11172 5 opensips 11174 5 opensips 11175 5 opensips 11177 5 opensips 11179 7 opensips 11181 1 opensips 11183 0 opensips 11185 2 opensips 11187 5 opensips 11189 5 opensips 11190 4 opensips [root@qorblpsisprxyd1 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 44 Stepping: 2 CPU MHz: 1197.000 BogoMIPS: 4266.58 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-3 NUMA node1 CPU(s): 4-7 Please advise for the fix as currently setting child processes to 10 in opensips config. Date: Thu, 19 Jan 2017 10:32:35 +0200 > From: Răzvan Crainea <[email protected]> > To: [email protected] > Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > When starting opensips, is there any opensips process that is using more > than 80% of a core? If so, can you pinpoint the PID in the opensipsctl > ps command? > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: > > > > Same with my case too. > > > > Regards, > > Agalya > > > > *From:*Users [mailto:[email protected]] *On Behalf Of > > *Ahmed Munir > > *Sent:* Wednesday, January 18, 2017 1:31 PM > > *To:* OpenSIPs Users <[email protected]> > > *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service > > > > Hi, > > > > I'm currently seeing the warnings when I start opensips service; > > > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: timer job <blcore-expire> has a 1500000 > > us delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: timer job <tm-timer> has a 1500000 us > > delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: timer job <dlg-timer> has a 1500000 us > > delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 2290000 us > > delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > INFO:core:do_action: max while loops are encountered > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: > > WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled > > for 190 ms (now 2470 ms), it may over > > lap.. > > > > I've tried to update the source code for timer.c (line#: 190) ref: > > https://github.com/OpenSIPS/opensips/commit/ > fd8f6ec442b4365da9d274af6939954246ece865?diff=split, > > but didn't work at all. > > > > Currently running 8 child processors, see below; > > > > [root@qorblpsisprxyd1 ]# opensips -V > > version: opensips 2.2.2 (x86_64/linux) > > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > > F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT > > ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, > > MAX_URI_SIZE 1024, BUF_SIZE 65535 > > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. > > main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 > > > > > > [root@qorblpsisprxyd1 ]# opensipsctl fifo ps > > Process:: ID=0 PID=3083 Type=attendant > > Process:: ID=1 PID=3085 Type=MI FIFO > > Process:: ID=2 PID=3086 Type=time_keeper > > Process:: ID=3 PID=3088 Type=timer > > Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 > > <http://10.3.120.94:5060> > > Process:: ID=12 PID=3104 Type=Timer handler > > > > I would like to know what changes required to fix this change? Please > > advise. > > > > > > -- > > > > Regards, > > > > Ahmed Munir Chohan > > > > > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.opensips.org/pipermail/users/attachments/ > 20170119/81b8d547/attachment-0001.html> > > > -- Regards, Ahmed Munir Chohan
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
