1) Regarding connection reuseoptimization,I haven't done any research on
this topic. In other words, libcurl will be managing its connections
through its default settings/ parameters, whichever they are. The module
is mature enough, maybe now is a good time to lookinto thisfeature.
2) Since you're doing lots of obviously blocking operations (HTTP
transfers), then you will definitely need more processes. However, I
noticed lots of transfers are quickly completed, withoutrequiring async,
so you don't want too many processes if all requests worklike that. Just
tune according to your needs until you find a sweet spot. You could even
share the performance results, I'd love to hear some feedback.
On 19.09.2016 17:57, Ramachandran, Agalya (Contractor) wrote:
Couple of questions for clarification.
1)I see for every HTTP request(for both sync and async), TCP ports are
being opened and closed.
Are we not using same port and pooling the request in
a particular port if we are hitting simultaneous requests?
2)Children parameter in the config file - I understand the use case of
this is to spawn multiple threads.
If we want to handle more load in OpenSIPS, we should increase this
So when increasing this number of children process we should take care
of CPU utilization and according to the no of CPU and RAM we used in
our Linux system.
Correct me if am wrong in my understanding of the above questions.
*From:*Liviu Chircu [mailto:li...@opensips.org]
*Sent:* Thursday, September 15, 2016 3:53 AM
*To:* Ramachandran, Agalya (Contractor)
<agalya_ramachand...@comcast.com>; OpenSIPS users mailling list
*Subject:* Re: FW:[OpenSIPS-Users] Asynchronous operation for REST queries
On 14.09.2016 21:33, Ramachandran, Agalya (Contractor) wrote:
Are you going to add one more parameter “connect_polling_interval”
and what will be use case of it?
Is it replacement for 10% wait time logic?
Also, I observed in the case of async call, it takes ~90 to 100ms
to open the port itself. Is this expected behavior?
Users mailing list