[Devel] Multiple IP's and UDP children
Aron Rosenberg
arosenberg at sightspeed.com
Tue Apr 3 19:15:58 CEST 2007
That works for us.
-Aron
SightSpeed Inc.
-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro]
Sent: Tuesday, April 03, 2007 10:14 AM
To: Aron Rosenberg
Cc: devel at openser.org
Subject: Re: [Devel] Multiple IP's and UDP children
I was rather thinking to keep the current meaning of "children" (number
of children per interface) and to have the ability to specify a number
of children when you define an interface - if a specific number is
forced, the default "children" will be ignored.
Ex:
children=5
listen=udp:ip1:port1/children=2
listen=udp:ip2
listen=udp:ip3
this will result in 5 workers per interface for ip2 and ip3 and 2
workers for ip1.
regards,
bogdan
Aron Rosenberg wrote:
> The ideal for us would be that "children" is the total number rather
> than a per IP:Port number.
>
> -Aron
> SightSpeed Inc.
>
> -----Original Message-----
> From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro]
> Sent: Tuesday, April 03, 2007 9:59 AM
> To: Aron Rosenberg
> Cc: devel at openser.org
> Subject: Re: [Devel] Multiple IP's and UDP children
>
> Hi Aron,
>
> no, at the moment there is no way to do that, but I guess it will be
> something very useful to have - I will keep it in mind....
>
> regards,
> bogdan
>
> Aron Rosenberg wrote:
>
>> Is there any way to set the number of children as a total value
>> instead of per IP:Port value? Our server listens on two IP:port
>> combos, and the traffic is split 90/10. However we have a huge number
>> of wasted children (and DB connections) since "children" is
duplicated
>>
>
>
>> for every IP:Port pair?
>>
>> -Aron
>>
>>
>>
>
------------------------------------------------------------------------
>
>> _______________________________________________
>> Devel mailing list
>> Devel at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>
>>
>
>
>
More information about the Devel
mailing list