On Tue, 2003-01-28 at 17:52, Kostas Kalevras wrote: > On Wed, 28 Jan 2003, Matt Scifo wrote: > > > I didn't even think to look in /proc. I found the same thing. The > > threads were spawned according to /proc, yet the daemon is not reporting > > thread info in the debug output. Though that still doesn't explain the > > horrid numbers I'm seeing. > > > > With only accounting enabled and authorization,authentication,session > > commented out, the number of requests per second should be much higher > > on my test box. > > > > Anyone have any ideas? > > > > Matt > > When you run top do you see one radius server process runing or more? > Also what is your cpu usage and especially your i/o (system) state percentage? > Try enabling only mysql accounting. Detail file accounting can be quite i/o > intensive so you shouldn't rely only on that to judge the server performance. > What are your accounting test packets? Are they start,stop records or both? >
I only see one radiusd dameon in top, and my cpu usage never gets higher than 30%, and thats on one cpu. The other 3 cpu's never get touched. Load average is negligible as well. I have tried running the server using just detail accounting, local sql accounting, remote sql accounting (which was less than 1/3 the original number of requests per/sec, probably due to firewall bandwidth throttling), and a combination of detail files and sql accounting. I tested with just start packets and also with start/stop packets using radpwtst v 1.52 from Radiator. Matt - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
