"Reprint" How to build a stress test environment for a large website

Tag: No online failed performed last operation TLB nbsp fail

Many friends want to do stress testing, in fact, not particularly difficult. Now there are a lot of tools. Let me introduce two tools for Microsoft.

1. Was:web Application strees Tool (free)

Application of was to the web for stress test instance detailed

Http://servers.pconline.com.cn/skills/0709/1119109.html

Official documentation (very detailed, suggested to read English version)

Http://support.microsoft.com/kb/313559/en-us

A test result report that I've done before

Creating was tests is usually done by recording, because it's a nightmare if you want to manually write those actions that request a click.

In addition, it can be based on the IIS log file (this is too useful), and a folder directory (this is also very interesting)

In fact, this is not the key issue, the key to know is that since the stress test, then what is measured? Don't get dizzy with these interfaces.

Stress testing is the main test is the server in the case of a large number of load situations will not have a performance bottleneck? If so, where is it?

To answer this question, in two ways

1. Page execution efficiency (usually there are several indicators that we are more concerned about)

Ttfb:time to FISRT byte receives the first byte of time.

Ttlb:time to last byte time of the final byte received

2.

When adding performance counters, pop up "failed to load perf counters from the computer xxx"

Both XP and Windows 2003 have encountered this problem, and have not succeeded anyway. Online search, they say it is only in Windows 2000 with this feature, crazy Dizzy

In addition to was, Microsoft offers a more powerful load testing tool, which is included in the so-called VSTS for tester release.

In general, in a large site testing environment, there will be so many machines

1. Controller (can be a developer's notebook)

2. Agents (usually desktop machines), can have multiple

3. Test server (Application deployed)

Three kinds of machines. In a domain environment, the controller and the agent must have the ability to access the performance counters of the test server. When working, the controller defines the test tasks and scripts, and when the test is started, the task is assigned according to the weights of each agent, and the agent initiates a request for the test server.

Finally, there are two basic principles in either was or VSTS.

"Reprint" How to build a stress test environment for a large website