[asterisk-bugs] [JIRA] (ASTERISK-22962) performance spike on Local channels originated using ARI

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp closed ASTERISK-22962.
----------------------------------

    Resolution: Fixed
    
> performance spike on Local channels originated using ARI
> --------------------------------------------------------
>
>                 Key: ASTERISK-22962
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22962
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging, Resources/res_ari
>    Affects Versions: 12.0.0-beta2
>            Reporter: Matt Jordan
>      Target Release: 12.1.0
>
>
> Using an AMI Originate with an optimizing Local channel:
> {noformat}
> action: Originate
> Application: Dial
> Data: Local/201 at queue
> Channel: SIP/200
> {noformat}
> Asterisk consumes about 6% cpu.
> With a non-optimizing Local channel, the consumption goes up quite a bit:
> {noformat}
> action: Originate
> Application: Dial
> Data: Local/201 at queue/n
> Channel: SIP/200
> {noformat}
> Asterisk now consumes about 17% cpu.  This seems to run with g722 on both ends.  There isn't any transcoding stuff in the output of Action: Status.
> With the call bridged via ARI, I see 57% cpu, with the transcoding stuff.
> So it may be ARI specific, or I guess it could be something I'm doing wrong when we create the bridge.  My bridge creation is a POST to "http://localhost/ari/bridges?type=".
> {noformat}
> Action: BridgeList reports:
> Event: BridgeListItem
> BridgeUniqueid: 6d05c058-7ec4-47d7-a029-08dca733ddfe
> BridgeType: basic
> BridgeTechnology: simple_bridge
> BridgeNumChannels: 2
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira