Hi team/Liviu,

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 number 
correct?
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.

Regards,
Agalya


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 <users@lists.opensips.org>
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?
Yes.


Also, I observed in the case of async call, it takes ~90 to 100ms to open the 
port itself. Is this expected behavior?
Yes.



Liviu Chircu

OpenSIPS Developer

http://www.opensips-solutions.com
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to