throttle them - ie, if the request rate is say 80/s or less then that is fine. if the requests come in faster, then the "smoothing" buffer would store them in a queue and then release them at a rate no quicker than the chosen rate, say 80/s.
of course, this buffering, can be done in an intermediate location (in a hardware router, for example), or on the servers themselves as a hook into the IP stack. i am aware that this just forms anothe queue but it seems to me that this might mitigate the problem where it is the high "rate" which knocks the servers out (might have nothing to do with the freeradius server, maybe the underlying OS, various freebsd 4.x), not the large queues. note that my earlier tests showed that slow queue processing were the limiting factor for another radius server i tested (not freeradius). i'm also aware that if teh smoothing queue is full then requests can be dropped - but it seems that at the moment this is not happening before the server gets "knocked out". i just wondered if anyone had tried such smoothing/throttling and whether new issues arose because of it. t -----Original Message----- From: Alan DeKok [mailto:[EMAIL PROTECTED] How would you "smooth" requests? Drop them? Slow them down? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
