Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.
Extreme Load testing
LegacyForum
Posts: 1,664 ✭✭
There may be times when the responses received for a load test may be in the region on 15MB, just due to the test you are running. Because of the Java heap size limitation on Windows, this may restrict the number of virtual users that can be used for this load test before an out of memory error occurs.
There are several ways around this:
You can set the following miscellaneous settings in the SOAtest Preferences panel’s Misc tab:
● Record All Traffic: Enables the recording of all traffic. Disable this option if you wish to improve memory performance by only storing traffic for failed tests. Enable this option if you wish to view the traffic from successful tests in reports. This option only affects reporting and does not affect the Traffic Viewer or any other output tools.
You can set the amount of memory allocated to SOAtest to the maximum allowed. -
"C:\Program Files\Parasoft\SOAtest\5.5.2\soatest.exe" -logex -memorymonitor -J-Xms1600m -J-Xmx1600m
-logex is for exception log, if exception is caught it's send to console or to GUI (and big red exclamation mark appears in lower-right corner) if you use st.exe instead of soatest.exe a soatest console appears, and you can see some output messages on it (see attached screenshot)
-memorymonitor open dialog with graph showing actual value of allocated and used memory (plus GarbageCollector button to run it! )
-J-Xms1600m -J-Xmx1600m allocate min/max number of memory for java heap space (
In a load-test you can ask SOAtest to "save individual hits"; this is a nice feature for debugging but also requires memory. Uncheck this option and rerun.
You can also get SOAtest to drop the incoming response by adding the attached Python script to the 'startup' directory in the SOAtest installation path. Please uncompress this file first ....
There are several ways around this:
You can set the following miscellaneous settings in the SOAtest Preferences panel’s Misc tab:
● Record All Traffic: Enables the recording of all traffic. Disable this option if you wish to improve memory performance by only storing traffic for failed tests. Enable this option if you wish to view the traffic from successful tests in reports. This option only affects reporting and does not affect the Traffic Viewer or any other output tools.
You can set the amount of memory allocated to SOAtest to the maximum allowed. -
"C:\Program Files\Parasoft\SOAtest\5.5.2\soatest.exe" -logex -memorymonitor -J-Xms1600m -J-Xmx1600m
-logex is for exception log, if exception is caught it's send to console or to GUI (and big red exclamation mark appears in lower-right corner) if you use st.exe instead of soatest.exe a soatest console appears, and you can see some output messages on it (see attached screenshot)
-memorymonitor open dialog with graph showing actual value of allocated and used memory (plus GarbageCollector button to run it! )
-J-Xms1600m -J-Xmx1600m allocate min/max number of memory for java heap space (
In a load-test you can ask SOAtest to "save individual hits"; this is a nice feature for debugging but also requires memory. Uncheck this option and rerun.
You can also get SOAtest to drop the incoming response by adding the attached Python script to the 'startup' directory in the SOAtest installation path. Please uncompress this file first ....
0