I've got Radiator running on two Sun Netra T1125s (ultra 300Mhz processors) using AuthBy File and a Unix-style password file. Radiator takes a *minimal* system load and handled hundreds of requests per second (I've got over 60 terminal servers distributed across two Radiator servers on two different machines). You're probably being bogged down by the SQL overhead -- the Perl DBD/DBI interface isn't the fastest piece of code. Is it possible for you to convert to a Unix style file? The reason I mention it is that Radiator caches the UNIX file in memory, meaning it can quickly retrieve information and reply to queries. I know it's a stretch to move from SQL to a flat file... but if performance is what you're after, that's the way to go. John At 11:34 AM 9/23/99 +1000, tom minchin wrote: >On Wed, Sep 22, 1999 at 04:42:33PM -0600, Bill wrote: >> >> I'm running 2.14 on a Sun Sparc20 that normally has a load between 2 and 3, >> AuthBy SQL'ing from a seperate machine who's load is usually less >> than 0.5. I've been doing some primative stress testing with >> radpwtest and requests start timing out at about 6-9 requests per >> second (2-3 sets of auth/start/stop). >> >> Fwiw, merit radius kept up with ~20+ request per second. >> > >Was Merit using SQL as well? > >One option is to run multiple Radiators on different ports (or same ports >and multiple interfaces). > >However, perl will not be as fast as C - you have to pay for flexibility at >some stage. > >[EMAIL PROTECTED] > >=== >Archive at http://www.thesite.com.au/~radiator/ >To unsubscribe, email '[EMAIL PROTECTED]' with >'unsubscribe radiator' in the body of the message. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
