Hi, From experience, what would be the best server configuration for 200,000 users with 75,000 concurrent users throttling 50,000 connections per second (with 1 NAS Client) in terms of: 1. Hardware configuration 2. Chooise of DB (PostgreSQL or MySQL) 3. FreeRadius Configuration (max_request_time, cleanup_delay, max_requests, max_servers, min_spare_servers, max_spare_servers, etc) Regards, Chris.
I am at the moment experiencing problem of load with mysql as acct DB (query failure during database backup of massive radius ticket injection) for a setup of 15000 concurrent users so I would recommend its use! Le 23.01.2009 17:54, tech.subscriptions@shepherdhill.biz a écrit :
Hi,
From experience, what would be the best server configuration for 200,000 users with 75,000 concurrent users throttling 50,000 connections per second (with 1 NAS Client) in terms of:
1. Hardware configuration 2. Chooise of DB (PostgreSQL or MySQL) 3. FreeRadius Configuration (max_request_time, cleanup_delay, max_requests, max_servers, min_spare_servers, max_spare_servers, etc)
Regards, Chris. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
From experience, what would be the best server configuration for 200,000 users with 75,000 concurrent users throttling 50,000 connections per second (with 1 NAS Client) in terms of:
Your network usage numbers look very wrong. 200,000 users are highly unlikely to use 75,000 concurrent connections and 75,000 connections are most unlikely to produce 50,000 requests per second - that would mean average session time of less than 5 seconds!!! 200,000 users with peak contention ratio of 10:1 and average session time of 10 minutes will produce about 100 requests per second at peak times. A single database might struggle with this peak rate. You should consider using something like buffered-sql virtual server: that will keep authentication working at max pace, while accounting might lag a few seconds at peak times but it will catch up when demand drops. Ivan Kalik Kalik Informatika ISP
If you have these figures, yours database has to be GOOD DB server and a GOOD machine.> To: freeradius-users@lists.freeradius.org> Subject: Re: Best Config> Date: Sat, 24 Jan 2009 11:08:53 +0100> From: tnt@kalik.net> > > >From experience, what would be the best server configuration for> >200,000 users with 75,000 concurrent users throttling 50,000> >connections per second (with 1 NAS Client) in terms of:> >> > Your network usage numbers look very wrong. 200,000 users are highly> unlikely to use 75,000 concurrent connections and 75,000 connections are> most unlikely to produce 50,000 requests per second - that would mean> average session time of less than 5 seconds!!!> > 200,000 users with peak contention ratio of 10:1 and average session time> of 10 minutes will produce about 100 requests per second at peak times.> A single database might struggle with this peak rate. You should> consider using something like buffered-sql virtual server: that will> keep authentication working at max pace, while accounting might lag a> few seconds at peak times but it will catch up when demand drops.> > Ivan Kalik> Kalik Informatika ISP> > -> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html _________________________________________________________________ Descubre cómo compartir tus fotos con Windows Live. ¡Pruébalo ya! http://home.live.com/
participants (4)
-
Alexandre Chapellon -
Santiago Balaguer García -
tech.subscriptions＠shepherdhill.biz -
tnt＠kalik.net