[RADIATOR] Radiator performance

[Hugh Irvine]

Hello Alex -

Yes you can try this - please let us know how you get on.

And please send me the trace 4 debug with LogMicroseconds so we can see what we're dealing with.

regards

Hugh


On 3 Feb 2010, at 19:24, Alex Massover wrote:

> Hi,
> 
> The solution looks to be a Farm. I didn't find it before because it looks to be new feature and I don't have it in 4.2 docs.
> 
> 
> 5.4.39 FarmSize
>       This optional parameter allows you to specify how many server instances to create in a
>       server farm. A server farm is a set of identical Radiator servers, all monitoring the same
>       RADIUS sockets. Incoming RADIUS requests are distributed among the child servers
>       in the server farm. The main server acts as a supervisor, and restarts children that die or
>       are terminated. Unix only. Defaults to 0, which menas no server farm, and only a single
>       instance of Radiator is run.
> 
>> -----Original Message-----
>> From: radiator-bounces at open.com.au [mailto:radiator-
>> bounces at open.com.au] On Behalf Of Alex Massover
>> Sent: יום ג 02 פברואר 2010 17:33
>> To: Bruno Tiago Rodrigues
>> Cc: radiator at open.com.au
>> Subject: Re: [RADIATOR] Radiator performance
>> 
>> Hi,
>> 
>> I'll do this test, that's good to know where exactly the problem is.
>> 
>> But even if it's SOAP endpoint's issue, it doesn't solve the problem.
>> Doesn't Radiator supposed to queue requests or something? The worst
>> thing I can expect is losing/dropping/not processing requests.
>> 
>>> -----Original Message-----
>>> From: Bruno Tiago Rodrigues [mailto:bruno.tiago.rodrigues at gmail.com]
>>> Sent: יום ג 02 פברואר 2010 17:16
>>> To: Alex Massover
>>> Subject: Re: [RADIATOR] Radiator performance
>>> 
>>> Your performance issues are, most likely, being caused by the SOAP
>>> endpoint.
>>> 
>>> You can benchmark RADIUS it by changing the authentication clause to
>>> INTERNAL and see how many requests does the server handle.
>>> 
>>> -B
>>> 
>>> On Tue, Feb 2, 2010 at 1:49 PM, Alex Massover <alex at jajah.com> wrote:
>>>> Hi!
>>>> 
>>>> 
>>>> 
>>>> What performance I can expect from single Radiator server?
>>>> 
>>>> 
>>>> 
>>>> Currently I’m getting timeout from clients with more than 20
>> requests
>>> per
>>>> second, on local LAN, with very low CPU usage and load average, on
>>> VMware
>>>> ESX, RHEL 5.
>>>> 
>>>> 
>>>> 
>>>> Is it OK and I should get more servers, or it supposed to handle
>> much
>>> more?
>>>> 20 requests per second doesn’t sound a lot for me.
>>>> 
>>>> 
>>>> 
>>>> My configuration is also very simple and SOAP endpoint always
>> answers
>>> fast,
>>>> no timeouts/rejects from there.
>>>> 
>>>> 
>>>> 
>>>> <Realm DEFAULT>
>>>> 
>>>>                 <Log SYSLOG>
>>>> 
>>>>                                 Facility local2
>>>> 
>>>>                                 Trace 5
>>>> 
>>>>                 </Log>
>>>> 
>>>>                 AuthByPolicy ContinueUntilAccept
>>>> 
>>>> 
>>>> 
>>>>        <AuthBy SOAP>
>>>> 
>>>> #              Fork
>>>> 
>>>>                                 Timeout 5
>>>> 
>>>>                Endpoint http://MSG-LB-BES-STG:80/SoapHandler.ashx
>>>> 
>>>>                SOAPTrace result
>>>> 
>>>>                SOAPTrace all
>>>> 
>>>>        </AuthBy>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 
>>>> Best Regards,
>>>> 
>>>> Alex Massover
>>>> 
>>>> VoIP R&D TL
>>>> 
>>>> Jajah Inc.
>>>> 
>>>> 
>>>> 
>>>> This mail was sent via Mail-SeCure System.
>>>> 
>>>> _______________________________________________
>>>> radiator mailing list
>>>> radiator at open.com.au
>>>> http://www.open.com.au/mailman/listinfo/radiator
>>>> 
>>> 
>>> This mail was received via Mail-SeCure System.
>>> 
>> 
>> 
>> This mail was sent via Mail-SeCure System.
>> 
>> 
>> _______________________________________________
>> radiator mailing list
>> radiator at open.com.au
>> http://www.open.com.au/mailman/listinfo/radiator
>> This mail was received via Mail-SeCure System.
> 
> This mail was sent via Mail-SeCure System.
> 
> 
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB: 

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets), 
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.