(RADIATOR) Dynamic Address Allocation Approaches

[Dean Manners]

Hey guys,
		We have been using <AuthBy DYNADDRESS> with
<AddressAllocator SQL> for a couple of years, mostly troublefree with MySQL.
However recently as our installation has expanded we are beginning to see
the process to be our next target bottleneck.  The infamous
outage+radiator+database scenario seems to be magnified for us now that we
have sizeable RADPOOL tables to manage - add an inch of MySQL replication
lag during high load periods and it gets really ugly :)

Im wondering what some of the other large installations approach to dynamic
allocation is? NAS assigned, DHCP, dedicated AddressAllocator database
servers?

Have been toying with the idea of pre-allocating dynamic addresses to users,
then devising some scheduled rotation system (..pretend dynamic). To take
the on-auth-decide-on-an-IP performance hit.


Regards
__________________________________________ 
Dean Manners

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.