JMeter

From Wiki:

JMeter is an Apache Jakarta project that can be used as a load testing tool for analyzing and measuring the performance of a variety of services, with a focus on web applications. JMeter can be used as a unit test tool for JDBC database connections, FTP, LDAP, Webservices, JMS, HTTP and generic TCP connections. JMeter can also be configured as a monitor, although this is typically considered an ad-hoc solution in lieu of advanced monitoring solutions. JMeter supports variable parameterization, assertions (response validation), per thread cookies, configuration variables and a variety of reports.
JMeter test scripts are fully supported by LoadIntelligence.

From JMeter Tips Blog: JMeter Tips

Posted Sun, 02/21/2010 - 00:35 by Cloud-Intelligence

 

JMeter Tips

Blog about performance/load/stress testing and JMeter software

From Tito's Blog: HowTo- Website Performance & Load Testing

Posted Fri, 02/12/2010 - 07:39 by Cloud-Intelligence

 

How To :- Website Performance & Load Testing -


Performance testing can be a tricky proposition, how many times have you deployed code that fell apart in production? (Hey, we’ve all done it!) Having a staging environment, which replicates the data and deployment environments are great first steps, but even that often falls short from producing reliable results. And that is where load testing comes in: we need to test our application in the context of a multi-user audience interacting with all of the components of our site. Great, but how do we do that? Well, why not just grab the access logs from your current production environment, and replay them!

From Theworkaholic Blog: Varying the data to the test

Posted Sat, 09/12/2009 - 08:23 by Cloud-Intelligence

 

Varying the data to the test - Motivation
The same test's need to be run, but the data we pass to it must be varied.
In addition further tests may need to change their behavior depending on the data. E.g. A user registering may provide different data , and subsequent screens may change depending on what the user has entered or may be skipped altogether. A common scenario is when a user registers to a site has various options he can choose from , and we need to test the behavior of the site for different combinations

In load testing you would want to subject your software to an equal amount of virtual users as in real production environment. You would then want to monitor the performance under the specified load, usually on a target-test environment identical to the production environment, before going live.

With traditional load testing the cost of building an environment and the priority of load testing versus on-going production tasks, are bringing decision-makers to make compromises and find less adequate solutions to the problem of validating performance under load and throughout time.

Syndicate content