SharePoint / WebServer Performance Tester "PerformanceTester.exe"

Resource Page Description
SharePoint / WebServer Performance Tester "PerformanceTester.exe" is a tool to create Stress for your WebServer. It make your bottlenecks, like: high CPU, high memory, long executions, ... visible and you can start troubleshooting your bottlenecks.

How it works?
Send HTTP-Request to aspx-Pages on webserver like the rootWeb of the site collection, e.g. http://mySharePointSite. If one instance of the tool did not create enought traffic then start a 2nd, 3th, ... instance. So you have more then one request in parallel. Bad Code can be identified in less then 5 instances.


Requirements
- .NET 2.0

Limits
- Supported authentication: Windows Integriert (NTML,Kerberos)
- (it use the current Windows-LogOn-Credentials)


PerformanceTester-Documentation

• get help: start performancetester.exe (run without any parameter)
• important Parameter:
• -url <URLValue>: e.g. performanceTester.exe -url http://myWebServer
• -i <Number>: Set the count of Request which were fired to the WebServer, e.g. performanceTester.exe -url http://myWebServer -i 10
• -d { 0 | 1 | 2 | 3 }: "debug mode" (display the time to receive for each request, Reads Header data from Response like Version, HealthScore,...), e.g. performanceTester.exe -url http://myWebServer -i 10 -d 1
• -out { 0 | 1 }: "output" (store the received html content in a file), e.g. performanceTester.exe -url http://myWebServer -i 10 -out 1

Request-Processing:

1. Send a Request
2. Wait until you receive an answer
3. Send next Request e.g.: with 10 Request.

Notice
After a test it’s important to check the IIS W3c-log and search for http status codes (500, 5xx, 40x,…) and the time-taken values. The PerformanceTester can also receive HTML-pages from IIS with standard Error messages like 404.

The first request is always a bit longer than the next ones. Suggestion: send eg. 10 Request to get a good average.