Product Comparisons
Apache JMeter
This chart shows a list of the differences between Web Performance Load Tester™ 2.7 and Apache JMeter 2.0 to the best of our knowledge.
| Feature | WPT | JMeter |
|---|---|---|
| Users simulated per computer | Most modern computers with 2GHz or better with 1G of RAM can simulate over 1,000 virtual users for most test cases. | A simple 6 web page test with images and think time between pages required 90 megs of RAM and used 90% of the CPU. |
| .NET | Automatically detects use of .NET specific technologies such as the VIEWSTATE and configures the test cases. | Every aspect of VIEWSTATE must be configured by hand. |
| Application State Management | Many application frameworks can embed the state of web-based applications anywhere, in hidden form fields, URL parameters, javascript. WPT's Application State Management feature automatically analyzes test cases for these techniques and configures them accordingly. | In order to support this type of thing you would have to spend days analyzing the HTML headers and content to figure out how your application is working, and then add multiple lines of code for each URL. Many of our customers have hundreds of state variables on each page, making it almost impossible to code by hand. |
| Multiple Sockets | Modern browsers open at least two simultaneous socket connections for each web page. WPT records and plays back using the same number of socket connections as the client. | Each virtual user opens a single socket connection. |
| SSL Support | Records and plays back SSL, including client certificates. | SSL playback only. |
| Think Time | Uses recorded think time for each web page, or can turn off think times for stress testing. | No way to record think times. No concept of a web page, only urls. Uses same value for each URL or or random values. |
| How many users can your website handle? | Gives a performance rating in terms of simultaneous users calculated from your site's own performance goals. | Not supported. |
| Which web pages are slow? | Sorted web page duration report identifies which pages are slow and under what conditions. | Not supported. |
| Usernames & Passwords | Authentication wizard automatically detects and configures usernames and passwords for form field, NTML (Windows Domain), client certificate, and basic authentication. | Supports form field and basic authentication, but they must be configured by hand by editing each URL. |
| Bandwidth Simulation | Virtual users can connect to the web server using different simulated bandwidths. With a load profile 50% of the users could connect using a DSL bandwidth, and 50% with 56K modem bandwidths. | Not supported. |
| Server Statistics | Collects memory usage and system load from the target web server. | Not supported. |
| Multiple Simultaneous Test Cases | Multiple test cases can be combined into a load profile based on percentages, where each case can be a different percentage of the total load and have other unique settings. For example, 20% of the users could be searching via modems, 20% searching via DSL, 20% making a purchase, etc. | A single test case can run at one time. |
| Load Balancing | The performance and memory usage of all test computers is monitored to insure accurate performance measurements. While controlling multiple computers the task of simulating users is load balanced among them using dynamic performance measurements of the test computers. | Not supported. |
| Multiple IP Addresses | Each virtual user can come from a different IP address. |
Not supported. |
| NTLM | Automatically supported in both recording and playback. | Not supported. |
| Session Tracking | The following session techniques are automatically detected and configured via a wizard:
Cookies URL rewriting URL parameter Hidden Form Field |
Session tracking must be detected and configured by hand by inserting controllers. |
