• English
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Pусский

Information may be Out-of-Date

This page about deprecated software versions is shown for
reference purposes only. Information on this page is not
maintained and may no longer be valid.

Please find the latest manual for Webserver Stress Tool here:

Manual Webserver Stress Tool (pdf)

Navigation: Contents   Index   Previous   Next


Webserver Stress Tool always writes a summary logfile during test. For more detailed logfiles, enable Write Detailed and User Logs. A detailed log (for the entire test) and an individual log for each user's activity will be written to disk.

Please be aware that for high traffic load tests with hundreds or even thousands of users, detailed logging can have a serious impact on the performance of the testing client and thus the measured values can be incorrect. It is always a good idea to run heavy tests with and without detailed logging to compare the results, specially keep an eye on the CPU load of the client.

Using Write Request Log (CSV), an additional machine readable logfile can be created that has one line of data per request of the test. This option is good if you need to process the results yourself. Note: The request log can also affect test client performance.

Choose Store logs in a ZIP file after test to store all the resulting logfiles as well as the configuration files of the test into one ZIP file for later reference. The file will be stored in the “zipped logs” subfolder of the EXE’s path and will show the date and time of the test in the filename.

You can immediately open the test report in your web browser or word if you enable Open HTML Report after test or Open WORD Report after test.

Webserver Stress Tool can also write all received data to the log file, select Write Header to Log for all data in the HTTP headers and Write data to Log for all HTML data of the requests.

When using Write on Error Only, only the data of requests that result in an error are written to the log.

Navigation: Contents   Index   Previous   Next