The value should be given in KB (kilobytes). This option limits the size of the log containing the response data. Limit the maximum response size written to the log Uncheck leads to escape any unprintable/control characters. If this option is checked, then LR escapes the binary zeros when printing request/response headers/body and/or JavaScript source. Print buffer escape for binary zeros only Note that you should use NeoLoad 5.1 to get improvements on the percentiles. If your SLA is that the response time should be under 3s, then if the percentile 95 (for example) is under 3s, it shows that 95 of the user have an experience that matches your performance goals. The durability of the app/website when challenged by peak user load. Whether the current infrastructure can sufficiently support a user’s interaction with the app/website without a hiccup. The maximum operational capability of the app/website.

The range of the field is from 50 to 2147483647. Percentile is often preferred, as it is performance goal oriented. Load testing must seek to understand: The number of users the app/website can support at any one time. As I mentioned above this option disable the wrapping of lines. This length is applied on request header, request body, response header, response body and JavaScript source. You can define the maximum length of lines which needs to be printed in the log file. The bolt thread pool size only limits how many bolt threads, neo4j server can concurrently handle. A thread can handle numerous connections. Figure 01: LoadRunner – Runtime Settings – Preferences – Logging The metric reports the maximum size of the bolt thread pool, where limiting the thread pool does not limit the total number of connections. You can also use this option to disable wrapping of the lines in the log file. Using this option you can control the printable length of request and response lines to be written in the logs. To provide more support on debugging of the script, application issues and error logs LoadRunner has ‘Logging’ option under the ‘Preferences’ tab of Runtime settings.

Neoload max response size