How to scope LoadRunner Vuser bursts

A LoadRunner Vuser burst is a short spike of simulated load created to stress a system at the moment of maximum demand. An audit that treats that spike as a permanent entitlement requirement charges for a peak the organisation reached once during a test and may never run again. Scoping the burst correctly, separating the brief maximum from the sustained level the license actually meters, is what keeps a Vuser finding tied to genuine capacity rather than to a single test event.

LoadRunner, the performance testing product that came to OpenText through the Micro Focus acquisition, exists to push systems to their limits, so high Vuser figures are not anomalies; they are the point of the tool. A capacity test deliberately ramps simulated users up to a peak to see how the system behaves under stress, then ramps back down. The Vuser count at that peak describes the test, not the steady state, and an audit that anchors the finding to the peak alone misreads a deliberate experiment as a baseline requirement.

What a Vuser burst is and why it spikes

A Vuser is a simulated user that generates load, and the way Vusers are licensed is set out in what is a Vuser and how is it licensed. During a load test the Vuser count is not constant: it climbs as the test ramps up, holds at a target, sometimes spikes higher in a stress or spike test, and falls as the test ends. The burst is the highest point of that curve, often reached for a few minutes to confirm the system survives a worst case. Treating that few minute maximum as the entitlement the organisation must hold permanently is the error that inflates the finding, the same overreach examined in how Vuser counting inflates a LoadRunner finding.

The distinction between a burst and a sustained level is exactly the distinction that decides a peak Vuser argument, the subject of can OpenText count peak Vusers against your license. Scoping the burst means establishing what the test was, how briefly the peak was held, and what level the entitlement was actually sized for, so the finding rests on the metric the license meters rather than on the highest number the logs ever recorded.

How to scope the burst against the entitlement

Scoping begins with the test itself. The LoadRunner controller records the Vuser ramp profile, so the logs show not just the peak but how long it was held and what the load looked like before and after. A spike sustained for three minutes during a stress test is a different fact from a load run continuously at that level, and the ramp profile is the evidence that distinguishes them. The controller and load generator architecture that produces these figures is described in LoadRunner Enterprise controller and load generator licensing, and reading it correctly is part of scoping.

The second step is to read the entitlement, because what the license meters determines whether a burst even matters. If the entitlement is sized to a sustained level with allowance for testing, a brief burst within the test window may not represent an overage at all. Confirming what was purchased and how it is measured is the reconciliation discipline set out in reconciling ALM entitlements before an audit, and it turns the raw burst figure into a question the entitlement can actually answer.

How the scope maps to the finding

The reason scoping decides the outcome is that the burst peak is the easiest number for an audit to cite and the least representative of genuine capacity. A finding built on the single highest reading treats a controlled experiment as a permanent state, while a finding scoped to the sustained level reflects what the system was actually licensed to handle. Shifting the basis from the momentary peak to the metered level is the core of the rebuttal, and the ramp profile is what makes that shift defensible rather than merely asserted.

This scoping also belongs inside the wider question of which environments and tests are even in scope, because a burst run in a non production test environment is doubly removed from a production entitlement requirement, the point developed in LoadRunner non production and test environment scope. A momentary spike in a staging test is not the baseline the license must cover.

How we scope a Vuser burst under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records, and the seven day notice clock starts immediately. Within that window we take over the single controlled channel and preserve the LoadRunner controller logs, the Vuser ramp profiles, and the entitlement together, so the shape of each test is captured rather than reduced to a single peak.

Reconstruct. We build the effective license position against entitlements and the Additional License Authorizations independently, establishing the sustained Vuser level the estate genuinely runs and distinguishing it from the brief bursts that stress tests deliberately create.

Rebut. We challenge every line that treats a momentary burst as a permanent entitlement requirement, presenting the ramp profiles that show how briefly the peak was held and the entitlement that defines the metered level. The finding falls from the burst peak to the sustained capacity.

Resolve. We settle on the count that reflects the metered level and, where it serves you, convert forward into an OpenPass agreement that records how LoadRunner Vusers are measured and how test bursts are treated, so the next review cannot anchor a finding to a single spike.

An anonymised outcome

Scoping matters because the remedy is severe. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so anchoring a finding to a momentary burst multiplies an unrepresentative number across every charge. Our anonymised case files show what separating the real peak from the noise achieves: a banking ArcSight finding driven by events per second was reduced from $6.0M to $1.8M, a 70 percent reduction built on splitting burst from sustained. A LoadRunner Vuser finding answers to the same reasoning, because a stress test spike is not a baseline.

Read the ramp before you accept the peak

The durable point is that a LoadRunner Vuser finding is scoped by reading the ramp profile, because a burst is a deliberate spike and the license meters a sustained level. A buyer who shows how briefly the peak was held and what the entitlement actually covers holds the finding to genuine capacity. To build the position, read what is a Vuser and how is it licensed, can OpenText count peak Vusers against your license, how Vuser counting inflates a LoadRunner finding, and LoadRunner non production and test environment scope. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If a LoadRunner finding rests on a burst peak, open a case.