Stress tests
How do I do properly load and stress test, given that I can't necessarily predict how or when my application complication components will be used?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

It is understandable that predicting the future is not possible, but knowing the present is possible. If you know the limits of the applications at the current state, then you gain two important benefits:

1) You can plan around its limitations, so that when load approaches the limits or is expected to approach the limits, you can act.

2) You have a performance baseline, which is a critical piece of data when making changes. It helps you detect performance issues as soon as they are introduced after changes in the application by rerunning the same load tests.

It's like driving a car. You know how many miles your fuel will last, but you do not necessarily know when it is going to run out. You refuel or take action when you reach these limits. The key is to know them first, and that is much more important than trying to predict future needs.

This was first published in May 2007

Back to top