n

Example Installations

Shown below are some examples of commercial Radiator installations. The details of each of these have been contributed by real Radiator owners. In some cases, identifying information has been omitted at the customer's request.

700,000 authentications per day

From Andy De Petter (adepette@krameria.net)

Hardware:
2 Sun Enterprise 220R servers (with both 2 X dual UltraSPARC-II 450Mhz processors) and 512Mb memory 2 Sun Enterprise 250 servers (with both an UltraSPARC-II 400Mhz processor) and 1Gb memory

Software:
Radiator 2.17.1 on the E220R servers authenticating against a MySQL database on the E250 servers, and also taking the E250 servers as their accounting database. Users are also capable of querying their online statistics, through a webpage.

Some figures:
Average around 350000 authentications per day (on each radius server, so ~700000 in total), which is around 8/sec avg (more than 30/sec during peaktime).

50 requests per second, 100,000 users

From a Radiator customer in Latin America:

some numbers from my servers:

• PIII 600Mhz windows NT radiator 2.14.1 doing accounting & authentication through stored procedures on a ms-sql server (on another machine), serves 20 auth/accounting stop requests per second (max). It consumes 5% cpu max. We share load on three servers of this kind

• PII 450Mhz FreeBSD 3.3 radiator 2.14.1 doing maxsession control (with mysql on another server) and auth by radius, using somewhat complex rewrite rules and handler criteria, can serve 30 requests per second. That would consume about 60% of the cpu; radiator might get unstable and grow to use all the cpu and ignore requests if forced to work beyond that. We share load between two servers of this kind

• PII 500Mhz FreeBSD 3.3 radiator 2.14.1 just doing a simple authby radius, can handle about 50 requests per second at 60% cpu.

Our complete radius system handles about 35 radius requests per second on peak hours without trouble.

80,000 users and 400+ NAS clients

We are so pleased with the product I can't really say enough about it. Here are some quick stats about how our connections broke down for the month of February, 2000:

12883796 Stop+Start records for Feb
444269 Stop+Start records/day
18511 Stop+Start records/hour
309 Stop+Start records/minute
5 Stop+Start records/second

5/second doesn't seem huge, but this is the average over a whole month. All of our sites are in the same timezone, so our peak hours greatly increase these numbers I'm sure. We only log Stop records in our SQL backend. We run Postgres but are seriously looking at moving to Mysql for some enhancements and issues we see (not related to radiator). We have 400+ Nas Clients and 80,000 dialup users. We run our main radius server on a dual PIII 500 running RedHat 6.1 We use the SQL Session Database as well.

50 requests per seconds

Running on a single CPU PIII 733MHz (Compaq DL380, 640Ram) I have been able to:

Authenticate 50 req/sec spread over 2 authentication processes handling each 20 and a third handling 10.
Log accounting for 40 req(start+stop)/sec spread over 2 accounting
processes handling each 20 (20 start+20 stop).

CPU was loaded to 90-95%

Most CPU usage by the accounting processes (about 60%)
The number of 20 has to do with LDAP queries taking 0.03 - 0.05
seconds per search in that particular environment.

The production environment handles LDAP queries taking 0.014 - 0.016 seconds so improvement can be expected.