Load Testing Blog
New Load Tester feature – web page performance goals
Load Tester has supported the concept of a performance goal for quite a while, but the implementation has been rather limited. We have completed work on an improved version for our next release (3.6). Load Tester now provides the ability to set a performance goal for each web page and/or transaction in a testcase individually. Of course, you can still specify a global page performance goal, as you could in the past. In addition, users can specify a default page (or transaction) duration goal for an entire testcase and then override that value for each page or transaction. The performance … Continue reading »
Load Engine simulates 3500 users on a single PC in performance test
We are frequently asked how many load engines will be needed to run a load test. Some general guidelines are provided here. Those guidelines were established using a fairly typical test scenario. With some tuning, we were able to tune the OS and Load Engine to simulate 3500 users on a single computer.
How many users should I load test my system with?
When customers are preparing to buy our load testing software, they frequently ask “How many users should I load test my system with?”. Naturally, we can’t answer that question without a lot more information about the performance requirements and the expected usage of the web application.
Load Testing a cluster of web servers
Ok – so you’ve spent months putting together a shiny new mission-critical web application, complete with multiple web servers, a few application and/or database servers. There is a load balancer in the mix or maybe you are using Microsoft NLB (Network Load Balancing). The system is nearly ready to deploy and it is time to run a load test. The first inclination is to fire up the load testing tool and throw the maximum expected load at the entire cluster. After all, there is no sense in wasting time with the smaller pieces, right? Wrong.
Load Test Configuration – using a stepped ramp
One of the most common load testing mistakes made by beginners is their configuration of the user ramp rate. This is best illustrated with an example configuration that we see frequently.
Load Testing .NET Applications
Introduction
Load testing is one of those steps that should be performed for every major system rollout but rarely happens. In this article, we will demonstrate the basic procedure for load testing web-based applications, using an ASP.NET application as an example.
Why Load Test .NET?
Working for a performance tools company, I have the opportunity to assist many companies with their load testing efforts. A large number of these efforts happen immediately before deployment or shortly after deployment, when live usage has determined that performance is inadequate. Naturally, performing the load testing at this stage in the project is much more costly than … Continue reading »