Diesel load testing software is a comprehensive tool for stress testing a website. Diesel Test is a software designed in Delphi 5, for systems under NT environment. It is distributed under the GNU LGPL license. Using Diesel load testing tool you will come to know about how your website will perform in the real world when hundreds, thousands, (or potentially millions) of users would place on your website. It is designed to test Internet web sites (HTTP and HTTPS requests), with monitoring and graphical representations.

1. Diesel Load Testing Tool

2. INTRODUCTION
• Diesel load testing software is a comprehensive tool for stress testing
a website.
• Diesel Test is a software designed in Delphi 5, for systems under NT
environment.
• It is distributed under the GNU LGPL license.
• Using Diesel load testing tool you will come to know about how your
website will perform in the real world when hundreds, thousands, (or
potentially millions) of users would place on your website.
• It is designed to test Internet web sites (HTTP and HTTPS requests),
with monitoring and graphical representations.

3. System Requirements
• Operating System:
• Microsoft Windows NT or 2000 or latest (32-bit)
• Processor:
• Pentium-class processor,
• RAM:
• 64 Mb.
• Performance:
• More memory and a faster processor will yield significantly better
performance.

4. Installation

9. How to Use?

13. Terminologies
• Diesel test uses the concept of "tests" and "scripts" to organize your
testing session.
• A test consists of one or more scripts.
• A script is a sequence of requests that a browser would make during
a normal session on your website.

14. Terms Explanation
Current Test: The filename of the current test.
Virtual Users: The number of virtual users that will be involved in the test.
Run time:
The duration of the test. Note that you can stop the test at any
time.
Use recorded host:
Normally, you will want to leave this checked. This is the name of
the host computer for the website. If it is unchecked, you can fill
in the host field to direct the script at a different computer.
Host: The name of the alternative computer hosting the target website.
Timeout:
The number of seconds to wait before the system records an
unsuccessful request as an error.
Use recorded think
time:
When you record a script, the system records how many
milliseconds elapsed between requests. If this box is checked,
then the requests are later played back at the same rate. If not,
then the system waits for "think time" seconds between requests.
Think time: The (optional) number of seconds to wait between requests.
User ramp-up
time:
When a test begins, the system adds virtual users one at a time,
rather than all at once. Adding them all at once would quickly
overwhelm a website. The user ramp-up time specifies the
number of seconds to wait before adding each new user.

15. Terms Explanation
Current Virtual
Users
The number of virtual users the system has created so far.
Pages Fetched The total number of requests.
HTTP Errors
The number of pages that came back with any HTTP response
code other than 200 - OK.
Timeout Errors
The number of pages that failed to come back within the allotted
timeout.
Other Errors
Any other error. If the website fails to respond at all, or
generates an unexpected disconnect, it would generate an
"Other" error.
Start Time The time the test started.
Time Remaining The time remaining in the test.

16. Terms Explanation
usernum An sequentially-assigned number for each virtual user.
requestnum
This corresponds to the request number in the script. The first
request is number 0, second request is 1, etc.
fetchstart
The time that the request was issued, measured in milliseconds
since midnight.
fetchend
The time that the request was completed, measured in
milliseconds since midnight.
result
A code of -1 or -2 means that the web server did not return a
response (a timeout or other error). For a detailed list of standard
HTTP response codes, see the Diesel test Appendices.

17. Terms Explanation
The Chart
•The chart is where the progress of the test can be seen.
•You can control the frequency with which the chart refreshes with the
refresh interval.
•Refreshing the chart does consume processor time, and too-frequent
refreshes will slow the system down. It will also show noisier data, because
values are averages over fewer requests.
Average Fetch Time
The average number of seconds it took to complete
a request to the server and receive a response since
the last measurement.
Max Fetch Time The time it took for the slowest page.
Users The number of virtual users.
The
Monitor
Tab
•This tab allows you to spy on the activity of one particular virtual user. It
allows you to see what the user would see. This is useful because it allows
you to spot unexpected results.
•Click "Enable Monitoring" to activate this function. Note that monitoring
does slow the system down and consumes system resources. Do not use it
during very heavy loads.
•The Monitor tab does not correctly show frames or embedded images.
Behind the scenes, though, these requests are being issued and measured.
The
Logging
Tab
•The Logging Tab is used primarily for debugging. It lets you see system
activity in detail. Using it slows the system down, so avoid using it for heavy
loads.

18. Results

21. Conclusion
The features of this software, although traditional, are
presented in an easy way for the user.
• Advantages:
• The quality of the chart
• The representation of the users created on the chart for a given time
• The capture tool
• Simple and fast to use
• Exporting the results
• The logging functionality

22. • Disadvantages
• The manual edition of the tests is badly designed
• Some results seem incoherent, particularly fetch times.
• The ambiguity of certain results
• Distributed tests are impossible
• No feedback from the target system
• Specific technology environment (Delphi, NT)