I ran across this article yesterday. It is nearly two years old, but the content is still entirely relevant. If you are building a system that needs to scale out to handle a large load, then you’ve probably already read this or something similar…if not, then it is worth your time.
What is the relevance to Load Testing, you ask? In section 5 author, Simon Brown, says”
“… set measurable goals throughout the system, verify and measure the real performance and consider performance at all stages of the project.”
For a project manager, a key part of the job is reducing risk of project failure. Reducing risk for a mission-critical project includes ensuring it doesn’t crash the day after deployment. It also includes reducing risk of missing deadlines. Load testing early in the project helps to reduce both of these risks by ensuring the software is stable and meets the performance goals. Fixing performance problems, especially those that limit scalability, is much less expensive (and time consuming) early in the project…so by load testing early in the project, cost is lowered and schedules are preserved.
Test early, test often!
Chris Merrill, Chief Engineer