Frequently Asked Questions
General |
|
| 1.1 |
How many virtual users can PureLoad simulate?
This is mostly depending on the particular user definition of the system to be tested. Other factors are which hardware is being used to generate load and how CPU/network intensive the performed operations are. The PureLoad license limits the number of virtual clients (worker threads). Each client can be used freely to simulate user behavior. As a rule of thumb, one can generally simulate one user with one virtual client or worker thread. Read more about Best Practices, Worker Threads in the documentation. |
| 1.2 |
How many worker threads can I use per worker?
This depends on the platform as well as which version of Java VM being used. For most cases it should be technically possible to use at least around 500 threads per worker. Such a high number of threads could make sense if running scenarios with a lot of sleep time, but otherwise it is not recommended. Also see Tuning PureLoad and the documentation Best Practices, Worker Threads |
| 1.3 |
My test seems to hang. What is happening?
The absolutely most common reason is that the server application does not respond. Try specifying a timeout for the tasks and see if the test continues (with a timeout being reported). |
| 1.4 |
I get "Port already in use" errors when trying to start PureLoad. Why?
If you get error messages when starting PureLoad servers saying something similar to: Error starting NamingServer at: host[192.168.10.1]:1099 Exception message is: Port already in use: 1099; ....This means that the specified port is used by another process. The most common reason is that you already have an instance of the PureLoad server running. Another reason could be that the specified port is used by another program installed on the machine. In this case you must choose another port for the actual process. Read about System Properties in the documentation for more information. |
| 1.5 |
Why do I get "Out of memory" errors?
If "Out of memory" exceptions appear in the worker log then you will need to increase the memory size of the worker JVM. To do this modify the worker.args property in the pureload.properties file found in the bin directory. For example to increase the max heap size to 128 Mbyte, change this as follows: worker.args=-Xmx256M -Xss256K" Note: Always keep the -Xss setting as is. If you run out of memory in the Console or the Naming, Taskspace or Manager server you must increase the heap size, defined in a file named program.vmoptions, where program is the program. You find these files in the bin directory.For example to increase the max heap size for the console to 512 Mbyte, change the console.vmoptions as follows: -Xmx512M" This exception may also be caused by running out of other OS resources, for example max. number of open file descriptors on UNIX (see Tuning File descriptors on a UNIX box(. Large scenarios that are executed many times (iterations) might cause the console to report out of memory problems. This is typically related to when the Update Interval setting in Tool Properties is set to low (polling to often). Increase the number of seconds and try again. Also see the documentaion, Best Practices, Long/Large Test Execution. |
| 1.6 |
Why do I see "Address already in use" errors, when executing tasks
If tasks fails with exception similar to:
"java.net.BindException: Address already in use: connect"
this means that you are out of TCP/IP connections on our
worker machine(s).
See Tuning Network
connections for more information.
|
| 1.7 |
I want to use PureLoad servers located outside of my firewall.
Can I do this?
Yes, but PureLoad uses RMI for internal communication between servers and the console By defalt there is no control over the ports being used. The solution is to specify all port being used and open up these ports in the firewall. Read more about this in the documentation, Best Practices, PureLoad and Firewalls. |
