PureEngage On-Premises

Hi ALL

    In a standalone OCS system, we've encountered a concurrency bottleneck where when concurrency exceeds 200 calls per second, there is a delay of up to 2 seconds between the SIP T-lab messages sent and the OCS receiving this message.

   How can I calculate the bottleneck in the interaction between SIP and OCS?  So that we can clearly identify which aspect of server resources needs to be expanded to resolve this bottleneck.

Please support ！

Thanks!

Robin OY

Robin, 200 cps would be excessive. 

OCS has only been performance tested by Genesys to 126 dials/second.   And OCS is a single threaded app, thus it is most likely it's main thread that is bottlenecked.  And you won't be able to add more CPUs, etc. to increase its performance.  If Windows, I believe you can use Process Explorer to look at the different threads and see the cpu load on it.

My recommendation is to deploy additional OCS instances and spread the load.  Even if it's on the same host.  Just use different ports.

Source:  Outbound Performance Testing