Server stress test

1. Go through. One user account goes through every operator, if it's OK, then do the stress test.

2. Concurrent. Users user-accounts go through every operator, if it's OK, then do the next step.

3. Random. Revoke accounts go through every operator randomly. This step may break server cache.

4. Time Stamp. Client shocould log the time for every operator in order to analyze server performance.

5. Exception catch. Client log this in order to log why it's failed.

6. use process not use thread in some time. web service will catch your client-threads in one session, though the Web service will assign one and only session ID to each thread. the server will replace one another.

7. Last time. Test Time shocould last as long as possible.

8. Clearly know which operator will cost the most (CPU, memory, network) in server. You can Fouse on it.

9. clearly know the envirnment and configuration of server.

10. clearly know the server application depends which kind of application (OS, DB)