Graeme Hinchliffe <[EMAIL PROTECTED]> wrote: > So this server is NOT short of grunt. However, if I fire a list of > 19000+ users in quick succession at the RADIUS server it quickly fills > the 5-10 SQL connections to the DB backend and begins rejecting all > the requests with the odd one authenticating.
As I said before, the server does not currently STOP grabbing new packets when it's too busy to process them. Lower the rate at which the packets come in, and it will be OK. Or, submit patches to the server to make it stop listening on the RADIUS port, until there's a free thread to handle the request. > If I increase the number of SQL connections to say 80 then more are > authenticated initially but at a VERY slow rate, and then after > 400-500 have successfully authenticated it begins to reject enmasse > again. Which is exactly the sign of the problem: the server is getting more requests than it can handle. > I must have something wrong in the configs somewhere, could someone > please point me in the direction of possible causes for this severe > performance hit? If you will look at the history of this list, you will see that the server has no problems handling 100's to 1000's of requests per second. If you're sending it 10,000+ requests in one second, you shouldn't be surprised that it's overloaded. You're attacking the server with a DoS attack. Of course it has problems... Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
