[RADIATOR] Radiator performance
Alex Massover
alex at jajah.com
Thu Feb 4 08:46:43 CST 2010
Hi!
But my problem is not about delay, it's about losing/not processing request.
For example I captured with wireshark an accounting request came to the server but no evidence to this request in radiator log. Meaning Radiator just silently ignored this request.
Farm didn't help, I experience the same behavior.
Radiator reports that there's no dropped request:
Reply-Message = "Radiator Radius server version 4.5.1"
Reply-Message = "Running on nj-radius-stg1.jajah.dublin since Thu Feb 4 12:19:53 2010"
Reply-Message = "6 Requests in the last second"
Reply-Message = "0 Access accepts"
Reply-Message = "0 Access challenges"
Reply-Message = "0 Access rejects"
Reply-Message = "0 Access requests"
Reply-Message = "9143 Accounting requests"
Reply-Message = "9143 Accounting responses"
Reply-Message = "0 Bad authenticators in authentication requests"
Reply-Message = "0 Bad authenticators in accounting requests"
Reply-Message = "0 Total Bad authenticators in requests"
Reply-Message = "0 Dropped access requests"
Reply-Message = "0 Dropped accounting requests"
Reply-Message = "0 Total dropped requests"
Reply-Message = "0 Duplicate access requests"
Reply-Message = "0 Duplicate accounting requests"
Reply-Message = "0 Total duplicate requests"
Reply-Message = "0 Malformed access requests"
Reply-Message = "0 Malformed accounting requests"
Reply-Message = "0 Total proxied requests with no reply"
Reply-Message = "0 Total proxied requests"
Reply-Message = "9143 Total requests"
Reply-Message = "0.162143349699178 Average response time"
> -----Original Message-----
> From: Hugh Irvine [mailto:hugh at open.com.au]
> Sent: יום ד 03 פברואר 2010 00:41
> To: Alex Massover
> Cc: radiator at open.com.au
> Subject: Re: [RADIATOR] Radiator performance
>
>
> Hello Alex -
>
> The best way to see what is happening with your authentications is to
> run Radiator with a Trace 4 debug and a LogMicroseconds logger
> (requires Time-Hires from CPAN) so you can see how long each processing
> step is taking.
>
> Something like this in your configuration file:
>
> .....
>
> Trace 4
>
> <Log FILE>
> Filename %L/microseconds-%Y-%m-%d.log
> # requires Time-Hires from CPAN
> LogMicroseconds
> Trace 4
> </Log>
>
> .....
>
> This will add a six digit microseconds offset in each debug timestamp
> so you can see where the delays are.
>
> Once we have the LogMicroseconds debug we can see exactly what is
> happening.
>
> regards
>
> Hugh
>
>
> On 3 Feb 2010, at 00:49, Alex Massover 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
>
>
>
> 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.
>
>
>
>
> This mail was received via Mail-SeCure System.
>
This mail was sent via Mail-SeCure System.
More information about the radiator
mailing list