Open source Tool for Stress, Load and Performance

Question

Possible Duplicate:
How do you stress test a web application?

Currently I have configured a project with cc.net, watin and nunit and now I want to do stress, load, and performance testing of my .net projects. Any idea which opensource tool should I use or cani achive it with same working tools and if yes then how?

Answer 1

Since you're allready familiar with c#. you can try this tool fwptt.sourceforge.net. It basically generates a test class in C# that you can modify as you wish and than run your test with that class.

Answer 2

Having the same problem and I'm using NTime - early days yet but it looks pretty good. Can run multiple threads for tests and other good features will report back here if anyone is interested.

I note that most answers here are for the Java/Web World neither of which match my requirements.

Answer 3

Try this : http://sourceforge.net/projects/dieseltest/

It seems the perfect thing.

Jaydeep Dave

Answer 4

I've used openSTA.

This uses a relatively simple script language.

You can easily test web services and write your own scripts.

It allows you to put scripts together in a test in any way you want and configure the number of iterations, the number of users in each iteration, the ramp up time to introduce each new user and the delay between each iteration. Tests can also be scheduled in the future.

It's open source and free.

It produces a number of reports which can be saved to a spreadsheet. We then use a pivot table to easily analyse and graph the results.

Answer 5

Jmeter hands down. It's the only tool I've ever used that has produced reliable results over and over. Once you get the hang of it, it's an absolute joy to work with and you can simulate a large load with a relatively small number of threads.

Answer 6

We use Grinder to run load/stress and functional tests against web services. We've never used it for web pages but its supposed to do that as well. You can really beat your servers up by installing the Grinder "agents" on a few machines that then spawn a bunch of processes to hit your site to simulate multiple connections.

The documentation is just OK, but what do you expect for an open source project?