On 01/04/2012 12:45 AM, Hugh Irvine wrote: >> I note that my current Radiator configuration results in only one >> connection to the backend postgresql db. Might there be some performance >> gains to be made in parallelising connections from radiator to the db? If >> so, how would I configure this in Radiator ? >> > > You would run multiple instances of Radiator - the easiest way to do this is > with "FarmSize n". > > See section 5.6.39 in the Radiator 4.9 reference manual ("doc/ref.pdf").
I'll just add one more possibility: you could consider a <Handler Request-Type=Accounting-Request> which would then use e.g. AuthBy HASHBALANCE to distribute accouting requests to multiple Radiator instances listening on loopback address. These instances would then push the accounting requests into the database. Thanks! Heikki -- Heikki Vatiainen <h...@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. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator