LoadRunner Analysis Tips and Tricks

Posted on February 25th 2010 by Joel Deutscher

I was looking to put together a list of LoadRunner Analysis reporting tips and tricks for our company Wiki. It didn’t take long however to find a comprehensive list by Nick Wilton.

I highly recommend taking a look at this list, and I have highlighted my top 5 tips below. To read the rest of Nick’s tips, or to leave him a thank you message, check out the full article over at JDS Australia here.

Continue Reading…

Using Regular Expressions in LoadRunner

Posted on February 10th 2010 by Joel Deutscher

It has previously been identified how to enable Regular Expressions in LoadRunner. A big thanks to Charlie, Tim for getting this working, and Dmitry for proposing the challenge.

In this post, I am to going demonstrate a practical use of bolting the regular expression engine ontop of LoadRunner. After all, it is more effort than LB/RB. So why go to all the trouble? Hopefully the following example will demonstrate a scenario where regular expressions can be invaluable.
Continue Reading…

Using Logparser with Perfmon logs

Posted on February 8th 2010 by Joel Deutscher

Logparser is an extremely useful tool for processing perfmon counters. It provides the ability to query text-based data such as log files, XML files and CSV files. This post will show you how to take a perfmon produced CSV file, and perform basic analysis on the results using logparser.

Continue Reading…

Performance Testing LDAP – Basics

Posted on February 5th 2010 by Joel Deutscher

LDAPA while back, I took some time to familariase myself with the Lightweight Directory Access Protocol (LDAP) from a performance testing standpoint. The following post is the outcome of that investigation and can provide a technical starting point for performance testing LDAP . It is not designed as a definitive reference and I implore you to submit corrections and improvements in the comments.

This post discusses several methods for testing the LDAP protocol using LoadRunner, one using JMeter, and a final using a PHP harness.

Continue Reading…

Execute the 100% Load Test First

Posted on January 11th 2010 by Joel Deutscher

There has always been something about performance testing that has bugged me over the years. It’s the standard approach of ramping up the amount of load on each test execution cycle.

The typical order of executions for a performance test is:

  1. Smoke Test
  2. 25% Load
  3. 50% Load
  4. 75% Load
  5. 100% Load

The flaw, as I see it, lies in the order of execution. I think we an improve on this concept by aiming to ramp down instead. Continue Reading…