Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Oct 2019 18:13:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 241620] net/asterisk16: 16.4.1 introduces performance issues
Message-ID:  <bug-241620-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241620

            Bug ID: 241620
           Summary: net/asterisk16: 16.4.1 introduces performance issues
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: madpilot@FreeBSD.org
          Reporter: ohartmann@walstatt.org
          Assignee: madpilot@FreeBSD.org
             Flags: maintainer-feedback?(madpilot@FreeBSD.org)

Running a small and simple PBX based on recent FreeBSD 12-STABLE (r354191: =
Wed
Oct 30 18:20:12 CET 2019 amd64), based upon a PCengine APU2C4, we realize a
mysterious issue in delayed actions and a higher CPU load, WCPU in top, in
contrast to prior versions.

Using PJSIP core.

The issue hasn't been investigated deeply, but when idling, the asterisk
process consumed not more than 2,5% WCPU, jumping from < 1% to > 2% and bac=
k.
Taking a call or performing a call (one user, up to three phones) took not =
more
than 6% load.
Now asterisk is most time at 4 - 6% load while idling. This wouldn't get my
attention if there were some other strange observations. On the console (CL=
I),
entered via "asterisk -rvvvv", we could watch when a call is made or a call=
 is
received by the typical data output visible in the console. Those messages
usually occured immediately even when taking or performing outbound calls a=
nd
especially calling local phones.=20

Now we observ the following: it takes up to three seconds after a number is
dialed, no matter whether outbound or local. It takes further three to four
seconds to show up the SDP messages and then again 2 -3 seconds until the p=
hone
called is ringing. The CLI is printing "ringing" messages, but it takes tho=
se
reported 2 - 3 seconds until the phone physically rings.

The same with inbound or outbound calls.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241620-7788>