[Serusers] Child procs

[Matt Schulte]

Ok, that makes a little more sense, thanks for clearing that up. However
what I'm noticing is that over a period of time the 4 "udp" procs lock
up, at random points from what I can tell. I can't seem to duplicate the
issue, by load testing or by load testing and waiting. One day our
production box "hung" 4 times. What's even more weird is this happens on
0.8.14, 0.9.0, and even latest cvs dev. To compensate I was raising the
child procs up to 100 until I found the problem, even with that many
procs still only 4 "udp" procs ever get generated. Also I disable TCP as
our infrastructure doesn't need it. Any suggestions? I don't want to
enable full debugging on production because I could never get debug to
run stable (duh?). Could this be a distro bug or some kind of lib
mismatch? I've read the manual many times, must be doing something
wrong. I love SER but getting to the point where we maybe forced to get
Asterisk to start proxying (gasp)..

Thanks, Matt

-----Original Message-----
From: Jan Janak [mailto:jan at iptel.org] 
Sent: Saturday, April 09, 2005 3:26 AM
To: Matt Schulte
Cc: serusers at lists.iptel.org
Subject: Re: [Serusers] Child procs


The children are not all equal. Some of them serve requests coming from
UDP, some of them from TCP and some are auxiliary, like the timer
process or the fifo server.

You can see the purpose of each children using serctl ps command.

If most of the traffic being processed by your server comes over UDP
then only the UDP receivers will be running and the TCP receivers will
be idle, but you still need them to be able to receive TCP based
traffic.

Optimum number of processes depends on your hardware and the amount of
traffic being processed. For common setups 8 children should be OK. 

  Jan.

On 05-04 07:26, Matt Schulte wrote:
> Does anyone have any opinions on this? What I'm worried about is of 
> course running out of procs and thus hanging SER, I believed this to 
> have happened several times..
> 
> 	Thanks..
> 
> -----Original Message-----
> From: Matt Schulte
> Sent: Monday, April 04, 2005 8:45 AM
> To: serusers at lists.iptel.org
> Subject: [Serusers] Child procs
> 
> 
> Do increasing child procs actually do anything? When I do a 'ps axu' I

> only show 4 of the procs having CPU time, the rest having no cpu time 
> at all. Any thoughts on this? Thanks, Matt
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers