Java Reference
In-Depth Information
• httperf (Web)
• WCAT (Web)
• Visual Studio Load Test (Web)
• SQLIO (SQL Server)
Choose a number and let's say you're going to see how the
system responds with 10,000 hits a minute. It doesn't matter
what number you choose because you're going to repeat this
step many times, adjusting that number up or down to see
how the system responds.
Ideally, you should distribute these 10,000 requests over
multiple load testing clients/nodes so that a single client does
not become a bottleneck of requests. For example, JMeter's
Remote Testing provides a central interface from which to
launch several clients from a controlling JMeter machine.
Press the magic Go button and watch your web servers melt
down and crash.
Step IV: Analyze Results
So, now you need to go back to your metrics you collected in
step 2. You see that with 10,000 concurrent connections, your
high availability proxy box is barely breaking a sweat, but the
response time with two web servers is a touch over five
seconds. Remember, your response time is aiming for two
seconds.
So,
we
need
to
make
refinements
to
the
configurations.
Step V: Remediate
Search WWH ::




Custom Search