I might be wrong. It's possible that each child process really does
create a DB connection handle, regardless of whether it's in a position
to use it.
This makes a certain amount of sense given that the specialisation of
each child process cannot be anticipated in advance; some child
processes might, for example, be asynchronous task workers which can
process elements of route script and thus potentially require DB access.
In that case, a small handful of database connection handles go to
waste. My heart bleeds for them. :-)
-- Alex
On 02/11/2016 08:45 PM, surya wrote:
I am not opensips expert, therefore, my understanding may not be correct but
when I see the log, I see the 4 child init and the print statements from the
child_init() method 4 times.
But, let me also clear some more things, I have modified the code to use
redis cache and I have put the create connection block in the child_init()
method and same I see in logs. Is this the correct way to create
connections?
Thanks,
Surya
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/A-doubt-on-count-of-child-processes-children-parameter-in-cfg-tp7601418p7601424.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
