Radiator has a tool called radpwtst for functionality and stress testing. It simulates a NAS sending access and accounting requests and receiving replies from the radius server.
I did a stress test on Radiator more than a year ago by running radpwtst on 4 boxes and Radiator on one linux box (PIII-500, 256MB) -- the radius server was able to handle at least 30 requests (access and accounting) per second. This is with both database and file logging. Brian Baquiran wrote: > > I am curious as to the stress-testing of radius. Did you actually > simulate >1000 people logging in *at the exact same time*, or just > people logging more-or-less at random until they totalled 1000? > Regardless of how many total users are logged in to the NAS, radius is > basically idle (that is, either sitting in a select() loop, or blocked > in recv()) unless someone logs in or out (an auth or start/stop accting > packet arrives from the NAS). > > Radius is simple enough that there should be very little inherent > performance overhead in any implementation. Your bottleneck will be your > logging functions (e.g. whether you insert into a database, write to > file, etc.) and whatever additional customizations you do yourself. > > Brian > _ > Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph > To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] > > To subscribe to the Linux Newbies' List: send "subscribe" in the body to >[EMAIL PROTECTED] _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
