In my tests, radclient has been /slower/ the radtest processes forked from a Perl script. 100 requests using my forking Perl script takes 2.2 seconds to complete. 100 requests using radclient takes ~8x, i.e 16.7+ seconds to complete. I'm using the variants included with 2.0.3 .. Using both -c and -p for radclient does not appear to actually fire off requests in parallel, then again, I have no immutable evidence showing this, other then the time it takes to complete. My test consists of a very simple auth request, only containing user name and password. Nothing else. Still, at this stage, the client side hosts are closer to a nuclear meltdown, whereas the server side is barely flinching. I want to be able to generate enough traffic to shoot the server down, or at least start seeing it get close to a crawl. I may be doing something wrong with the radclient, that is a possibility as well ... //anders ----- Original Message ----- From: "Ivan Kalik" <tnt@kalik.net> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Friday, May 9, 2008 4:26:37 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: Load testing tool recommendation http://wiki.freeradius.org/Radclient Ivan Kalik Kalik Informatika ISP Dana 9/5/2008, "Anders Holm" <anders.holm@sysadmin.ie> piše:
So, I'm building a complete solution, from scratch.
As such, the business owners have some requirements on how many requests it should be handle today per second and "some point in the future" as well.
Would there be any good load testing tools, or some handy way to figure out how many tps my current setup can handle?
I've got a dirt simple Perl script that forks out x radtest processes and I'm just right now seeing how many a second I can ship. Problem being, the RADIUS server is happily letting me melt down to "client" systems, without breaking a sweat. I'd like to load the server, not the clients .. :) I want to see where it eventually breaks down, which seems a task in its own right.
Any pointers would be much appreciated. I'd rather have something I can fire off from command line then a GUI solution, for obvious reasons.
Cheers!
//anders
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Anders Holm wrote:
In my tests, radclient has been /slower/ the radtest processes forked from a Perl script.
100 requests using my forking Perl script takes 2.2 seconds to complete. 100 requests using radclient takes ~8x, i.e 16.7+ seconds to complete.
You can run "radclient -x" to see what it's doing. Printing the sent/received packets slows it down, but not that much. When I run "radclient -q -c 10000", I can easily run 5k packets/s to the local machine. My tests from remote machines are a little slower, but not 5 packets/s. I'd say there's something wrong in your network, but I'm not sure where. Alan DeKok.
Dear Alan o Ivan: I am trying to download pam_radius_auth.so module from freeradius.org but I think it's down now.
Hi,
Dear Alan o Ivan:
I am trying to download pam_radius_auth.so module from freeradius.org but I think it's down now.
pam_radius_auth.so is a precompile shared library file. do you mean the main package? if so, http://www.freeradius.org/pam_radius_auth/ is fine here alan
Wireless could be the problem if you have some wireless links between radius server and your NAS. Alan DeKok wrote:
Anders Holm wrote:
In my tests, radclient has been /slower/ the radtest processes forked from a Perl script.
100 requests using my forking Perl script takes 2.2 seconds to complete. 100 requests using radclient takes ~8x, i.e 16.7+ seconds to complete.
You can run "radclient -x" to see what it's doing. Printing the sent/received packets slows it down, but not that much.
When I run "radclient -q -c 10000", I can easily run 5k packets/s to the local machine. My tests from remote machines are a little slower, but not 5 packets/s.
I'd say there's something wrong in your network, but I'm not sure where.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Nope, no wireless involved. Good thought though! :) //anders ----- Original Message ----- From: "Marinko Tarlac" <mangia81@gmail.com> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Sunday, May 11, 2008 4:01:57 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: Load testing tool recommendation Wireless could be the problem if you have some wireless links between radius server and your NAS. Alan DeKok wrote:
Anders Holm wrote:
In my tests, radclient has been /slower/ the radtest processes forked from a Perl script.
100 requests using my forking Perl script takes 2.2 seconds to complete. 100 requests using radclient takes ~8x, i.e 16.7+ seconds to complete.
You can run "radclient -x" to see what it's doing. Printing the sent/received packets slows it down, but not that much.
When I run "radclient -q -c 10000", I can easily run 5k packets/s to the local machine. My tests from remote machines are a little slower, but not 5 packets/s.
I'd say there's something wrong in your network, but I'm not sure where.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Anders Holm -
Marinko Tarlac -
Yago Fdez. Hansen