Performance Testing

Loadrunner : Error -26601: Decompression function wgzMemDecompressBuffer failed, return code=-5 (Z_BUF_ERROR), inSize=0, inUse=0, outUse=0

The “error -26601: Decompression function wgzMemDecompressBuffer failed, return code=-5 (Z_BUF_ERROR), inSize=0, inUse=0, outUse=0″ in loadrunner occurs because of insufficient buffer size set in the runtime settings. The Network buffer size is set to 12288 bytes, by default. In a scenario where user requires to use more than the specified buffer,…

Important performance counters for .net applications

The following performance counters for .net applications, can act as general guidelines for different performance problems, related to the .net application under test. • Processor\% Processor Time • Process\Working Set • Memory\% Committed Bytes in Use • Memory\% Available Mbytes • Memory\% Pages/Sec • Memory\% Page Faults/Sec • PhysicalDisk\% Idle…

LoadRunner Controller Error :- Server has shutdown the connection prematurely

The Error “Server has shutdown the connection prematurely” is often seen during performance test execution in controller. 1. Is this a performance issue with the web/app server? No, it is not. 2. Is this related to Loadrunner? Yes, it is. 3. Can we resolve it by simply setting web_set_sockets_option (“IGNORE_PREMATURE_SHUTDOWN”, “1”);…

How to resolve LoadRunner 500 internal server error while testing an upload file scenario

Scripting a file Upload scenario is usually pretty straightforward, just do few correlations and the script runs without any errors. But, sometime it becomes complicated when script keeps failing even after correlating all the dynamic values. The most common error encountered while executing the upload script is LoadRunner 500 internal…

How to Pinpoint Memory bottlenecks

The basic symptoms of memory bottlenecks that affect application performance are – Memory leak Memory usage slowly increases over time Performance degrades Application will freeze/crash requiring a restart After restart application is running fine again, and the behavior continues Excessive memory footprint Application is slow to load After load, other…