Every Test Ends With a Score
One honest, explainable number per run — computed from your own transactions, not from injected benchmark executables. Click a score chip to open the run summary, drill into the five measures, and generate the built-in PDF report.
Test Runs
Every completed test carries its LoadGen Score, verdict and regression status.
| Score | Load profile | Type | Started | Duration | Users | OK | Failed | Status | ||
|---|---|---|---|---|---|---|---|---|---|---|
| Citrix Enhanced | Citrix Enhanced | 25 Jun 14:23 | 01:00:00 | 11 | 9 | 2 | Completed | |||
| Citrix Enhanced | Citrix Enhanced | 24 Jun 22:10 | 00:41:22 | 11 | 8 | 3 | Partial | |||
| AVD - Marketing | AVD | 23 Jun 09:04 | 00:22:11 | 8 | 5 | 3 | Partial | |||
| Horizon - Finance | Omnissa Horizon | 22 Jun 17:52 | 00:55:03 | 12 | 12 | 0 | Completed | |||
| Citrix Enhanced | Citrix Enhanced | 21 Jun 12:31 | 01:00:00 | 10 | 8 | 2 | Completed |
What the LoadGen Score Is
One number a CTO can quote, an engineer can decompose, and a report can lead with.
0–100 scale, also displayed as 0–10. A word verdict with every number. Shown everywhere a run appears. Honest about gaps: partial runs are marked partial, unbaselined runs say so instead of pretending.
Five Measures, One Score
A weighted sum of five measures. Every measure computed from the run itself.
Click any measure to drill in. Try “omit a measure” to see the score re-normalise in real time — exactly what the product does when a component cannot be measured.
This run's formula
Score = 30.4% Reliability + 30.4% Responsiveness + 13% Consistency + 13% Trend vs baseline + 13% Infrastructure
No hidden weights. When a component cannot be measured (no baseline, no per-machine CPU), it is left out and the remaining weights grow to keep the total 0–100.
Verdict legend
- Excellent90+
- Good75–89
- Fair60–74
- Poor40–59
- Critical<40
Try it
Click any measure to drill down to its definition. Try “omit a measure” below to see the score re-normalise in real time.
Omit a measure
Built From Your Applications
Not benchmark executables. Your business applications.
| A typical synthetic experience score | The LoadGen Score |
|---|---|
| Weighted average of timers from dedicated benchmark programs injected into the session | Weighted measures computed from timings of your actual applications in the workload you authored |
| Tells you how benchmark executables performed on the machine | Tells you how your business applications performed under load |
| Score inputs are fixed by the vendor | Score inputs are your own transactions and measurements, openable down to the samples |
Understand the Run
The report is the handout. The dashboard is the conversation.
Beyond the report, every run's data is queryable in Analyse: build dashboards, compare 2–5 runs side by side, and chart percentiles, trends and distributions with an AI assistant on the dashboard itself.
Analyse · Dashboard
Real charts over run data — baseline vs current.
Analyse · Citrix Enhanced dashboard
Updated 3 min ago · owner: LoadGen · 6 panels · 2 comparison series
Baseline-Aware by Design
The second test you ever run is already a comparison.
- ▸ Pick any earlier run of the same profile as the baseline. The previous finished run is suggested automatically.
- ▸ The score's Trend measure and the run summary's Regressions line are computed against it. “None vs baseline” is a real, earned statement.
- ▸ Reports with a baseline show what improved and what regressed since the previous run: release over release, patch over patch.
- ▸ No baseline available? The run is scored on the remaining measures and clearly marked unbaselined. Never a fabricated trend.
Screenshots Captured During the Test
Numbers tell you what happened. Screenshots show you what it looked like.
- Agents capture screenshots during the run, tied to the transaction and sub-transaction being executed at that moment.
- Each screenshot carries its timestamp and an optional message (for example the error that triggered it).
- De-duplicated by content: a repeating error stores once, not five hundred times.
- Surface alongside the run's results and feed the AI-assisted analysis.
The Six-Step Load Test Flow
Six steps, one platform.
How a test moves through LoadGen, from idea to decision. Steps 4–6 happen without any extra work from you.
Author
Platform wizards (Citrix, RDP, AVD, Omnissa) capture the scenario. Version-controlled .lgs workloads. Phases: Idle, Ramp-Up, Sustain, Ramp-Down.
Deploy
The Launcher Appliance turns a downloaded VM image into enrolled, update-managed, preflight-checked agents.
Execute
The live cockpit streams concurrency, errors/s and phase progress in real time. Pause, resume or stop at any moment.
Score
The run ends with its LoadGen Score, verdict and regressions-vs-baseline. Automatically.
Understand
One-click PDF report, comparison charts (2–5 runs side by side), percentiles, trends, and AI analysis of the full run context.
Decide
Baseline, trend and capacity evidence. Before: guess. After: measured.
Who Reads What
The same run answers three different people. Nobody has to translate.
Engineer
Drills from the score into measures, samples and screenshots.
IT Manager
Watches verdict and trend across releases.
Business
Gets one number per release and a PDF that explains it.
Run a Test. Get a Score. Hand Over the Report.
Every completed test includes the LoadGen Score and the built-in management report. No extra tooling, no spreadsheet evenings.
