There is no clear cut answer to this, but we’re happy to provide guidance.
Your business liaison (usually a product manager, project manager, or analyst) may know the answer right away, since there may be specific business goals associated with the project.
The system architect may also have a good idea of what the capacity of the overall system is, so that might be another place to start asking.
You should also read our FAQ on hits/second vs. concurrent users, as that may help you better think about how many virtual users you need in a load test.
When in doubt, a good rule of thumb (but certainly far from accurate) is that a single web server can handle roughly 250 to 500 concurrent users. So if the environment you’re testing has two web servers behind a load balancer, it’s reasonable to expect it can handle between 500 and 1000 concurrent users from BrowserMob.
Warning! Even if you have reasonably good confidence that the system can handle hundreds or thousands of users, we strongly encourage you to start small, ramping up and scheduling several tests over time. This will almost certainly catch any simple performance errors early on, before you’ve spent a lot of time and energy on larger tests.
Recent Comments