Applies to ReadyAPI 3.0, last modified on December 06, 2019

During test runs, LoadUI collects data on the target web service performance to help you learn how your web service behaves under the load.

However, when LoadUI runs a large load test for a long period of time, collecting and storing a large amount of test data can consume a lot of your machine memory. This may slow down the test run or cause other performance problems in LoadUI.

To avoid possible performance issues and run large load tests more efficiently, reduce the amount of collected data:

  • Disable data collection for reports (in LoadUI Pro). Printable reports in LoadUI gather current data on test runs. You can turn off the data collecting to reduce the amount of time and memory it takes to get and store the collected data:

    1. Click Preferences on the toolbar or select File > Preferences from the main menu.

    2. In the ReadyAPI Preferences dialog, select ReadyAPI.

    3. Select Disable Reporting.

    API load testing with ReadyAPI: Disable reporting to preserve memory option

    Click the image to enlarge it.

  • Reduce the amount of data LoadUI collects for assertions. Assertions you add to your load tests verify that the test results meet the specified criteria and report errors if those criteria are violated. Configure LoadUI to collect only brief data on assertion errors:

    1. Click Preferences on the toolbar or select File > Preferences from the main menu.

    2. In the ReadyAPI Preferences dialog, switch to the ReadyAPI tabbed page.

    3. Clear the Complete Error Logs check box.

    API load testing with ReadyAPI: Logs complete messages to reports on errors

    Click the image to enlarge it.

  • Limit the amount of points used to draw charts. The long load tests may require a lot of memory to draw the full charts. To avoid possible issues, use the ‑Dloadui.charts.maxpoints=<value> JVM option to set the maximum number of points used to draw a chart. When LoadUI reaches the specified number of points, it removes the oldest one from the memory, so the beginning of the chart is not drawn. It affects graphs shown on the Load page, graph views on the Statistics page, and graphs exported to printable reports.

    This option affects only information used to draw charts. You can examine statistics of the entire test by using table views.

Note that the Discard Successful Results option of the underlying test case does not affect the load testing. LoadUI always discards successful results during the load test run.

  • Discard responses. To reduce the memory used to simulate test steps, configure the functional test on which your load test step is based to discard responses returned from the target web service:

    1. In SoapUI, open the test case on which your load test is based.

    2. Select a test step and switch to the Request Properties tab.

    3. On the Request Properties tab, set Discard Response to true.

    Discard Response property
  • Keep the response window closed during the test run. To prevent LoadUI from collecting response data during the test run, close the Response window. Otherwise, LoadUI will collect and display response data regardless of settings you configured.

See Also

Preferences
Test Steps

Highlight search results