25 Jun
2007
25 Jun
'07
1:17 p.m.
Papadopoulos Georgios wrote:
either or
a)For some reason the first child is the lucky one and receives most of
the incoming threads?
b)Maybe there is a bug. I think there are some tasks which are only done
by the first child - e.g. loading the location table at startup.
regards
klaus
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: Monday, June 25, 2007 9:28 AM
To: Papadopoulos Georgios
Cc: Bogdan-Andrei Iancu; users(a)openser.org
Subject: Re: [OpenSER-Users] RE: [Users] out of memory - please help
Papadopoulos Georgios wrote:
Then how do you explain that only the first child ran out of memory? Why did this only appear on the first receiver
child? I
would expect
that all children receive an equal amount of
traffic so they should
all run out of memory more or less at the same time. Except
if when a
message is received, Openser finds the first
available
child and does
this by trying child 1,2,3... Is this the case?
The distribution between the UDP listener threads is not done
by openser but by the OS. openser will open port 5060 and
then fork the process "children=..." times. Then, all
processes will read from the same port.