[asterisk-bugs] [JIRA] (ASTERISK-26088) Investigate heavy memory utilization by res_pjsip_pubsub

[Richard Mudgett (JIRA)]

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

Richard Mudgett updated ASTERISK-26088:
---------------------------------------

    Description: 
Under *heavy* subscribe/unsubscribe load Asterisk will keep consuming memory until the process runs out of memory.

Using a sipp scenario that does the following for each user:
# REGISTER
# SUBSCRIBE to 8 extens
# wait
# unSUBSCRIBE from those extens
# unREGISTER

When simulating a lot of user endpoints the system taskprocessors get backed up.  This can be seen by running CLI "core show taskprocessors" and watching several taskprocessors get backlogged.

Another thing noticed during investigation is that these messages were seen a lot:
{noformat}
sip_transactio Unable to register REGISTER transaction (key exists)
sip_transactio Unable to register SUBSCRIBE transaction (key exists)
{noformat}


  was:
Under *heavy* subscribe/unsubscribe load Asterisk will keep consuming memory until the process runs out of memory.

Using a sipp scenario that does the following for each user:
# REGISTER
# SUBSCRIBE to 8 extens
# wait
# unSUBSCRIBE from those extens
# unREGISTER

When simulating a lot of user endpoints the system taskprocessors get backed up.  This can be seen by running CLI "core show taskprocessors" and watching several taskprocessors get backlogged.


> Investigate heavy memory utilization by res_pjsip_pubsub
> --------------------------------------------------------
>
>                 Key: ASTERISK-26088
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26088
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/Sorcery, Core/Stasis, Resources/res_pjsip, Resources/res_pjsip_pubsub, Resources/res_pjsip_registrar
>    Affects Versions: 13.9.1
>            Reporter: Richard Mudgett
>            Assignee: Richard Mudgett
>
> Under *heavy* subscribe/unsubscribe load Asterisk will keep consuming memory until the process runs out of memory.
> Using a sipp scenario that does the following for each user:
> # REGISTER
> # SUBSCRIBE to 8 extens
> # wait
> # unSUBSCRIBE from those extens
> # unREGISTER
> When simulating a lot of user endpoints the system taskprocessors get backed up.  This can be seen by running CLI "core show taskprocessors" and watching several taskprocessors get backlogged.
> Another thing noticed during investigation is that these messages were seen a lot:
> {noformat}
> sip_transactio Unable to register REGISTER transaction (key exists)
> sip_transactio Unable to register SUBSCRIBE transaction (key exists)
> {noformat}



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