[RADIATOR] Radiator Performance

[Hugh Irvine]

Hello James -

This is a "how long is a piece of string" question, as almost everything depends on the external resources that Radiator is using.

In other words, Radiator performance is almost always dependent on things like SQL and/or LDAP databases.

Radiator itself using an in-memory cache can do thousands of requests per second, but real world performance with SQL tends to be more like hundred(s) per second, and LDAP tends to be more like ten(s) per second.

YMMV - note also that in a production environment you should be using things like multiple Radiator hosts with load balancer(s).

For testing you should put together a "proof of concept" development system and run some tests with "Trace 4" and "LogMicroseconds" so you can see exactly how long each processing step is taking.

See the example configuration files in the "goodies" directory, and the Radiator reference manual in "doc/ref.pdf".

regards

Hugh


On 24 Jul 2012, at 03:13, James Austin wrote:

> Hi,
>  
> Are there any published measurements on the number of transactions per second your AAA product is capable of achieving running on a windows OS based server?
>  
> Regards,
>  
> James Austin
> Manager Technology & Projects
> Crystal Communications Ltd.
> 281-300-8294  Mobile
> 281-361-5199  Office
>  
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator


--

Hugh Irvine
hugh at open.com.au

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. 
Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.