DeNamiK is proud to present the DeNamiK LoadGen 2.1. With the DeNamiK LoadGen it's possible to perform the following actions:
- Load test
- Stress test
- Performance test
- Constant monitoring
- Benchmark
- Reporting
Load testing
From Wikipedia, the free encyclopedia
Load testing is the process of putting demand on a system or device and measuring its response.
When the load placed on the system is raised beyond normal usage patterns, in order to test the system's response at unusually high or peak loads, it is known as stress testing. The load is usually so great that error conditions are the expected result, although no clear boundary exists when an activity ceases to be a load test and becomes a stress test.
Massive load and stress tests, either in test or production environments, are now easier than before. Record and create user action scripts with the DeNamiK User Action Framework. No necessary changes to the Citrix (XenApp), Microsoft Terminal Server (RDP / RDS) and Quest vWorkspace servers. Just make sure you have created a user action test script with the DeNamiK User Action Framework and have enough workstations available to launch the sessions! With the DeNamiK LoadGen - Director you can manage the LoadBots (workstations which provide the sessions), create your scenario's, fire away ICA or RDP sessions in a manageable fashion to properly evaluate your Citrix (XenApp), Microsoft Terminal Server (RDP / RDS) and Quest vWorkspace environment and also get a report containing the passed stages of the ICA or RDP sessions.
This document will outline how to enable simultaneous sessions launched from the LoadBot machine. In our standard setup we don't allow the DeNamiK LoadGen - Director and LoadBot to be running simultaneous sessions from one LoadBot due to possible performance problems. We will assume that you have installed the DeNamiK LoadGen - Director on the %MachineName% (local machine name) and the LoadBot name will be %LoadBotToEdit%.
This document will outline how to run the DeNamiK LoadGen - Director and LoadBot process on the same physical machine. In our standard setup we don't allow the DeNamiK LoadGen - Director and LoadBot to be running on the same machine due to possible performance problems. We will assume that you have installed the DeNamiK LoadGen - Director on the %MachineName% (local machine name).
This document will outline a problem which can occur when trying to activate a LoadBot when the DeNamiK LoadGen - Director and the LoadBot resides in separate physical Active Directory domains. It's possible to have a trust between these domains.