Skip to main content

PerForge v2.1.12: New Version

· 2 min read
Uladzislau Shklianik
Uladzislau Shklianik
Performance engineer
Siamion Viatoshkin
Siamion Viatoshkin
Performance engineer

PerForge v2.1.12 brings two meaningful improvements: full control over how aggregated tables look in your reports, and correct metric aggregation for distributed JMeter setups running across multiple injector nodes.

1. Aggregated Table Customization​

Until now, the ${aggregated_data_table_} variable in report templates always produced the same fixed output — all metrics, all columns, in the same format. In 2.1.12 you can fully control what that table looks like through the new Reporting Table section in Advanced Settings.

Choose your columns​

Select exactly which metrics appear in the table and give each one a meaningful display name. Instead of raw keys like pct90 or avg, your reports can show P90 Response Time or Average RT — whatever makes sense for your audience. Unused metrics are simply omitted.

Split baseline and current into separate columns​

When a baseline test is selected, the default format shows values as 20.00 → 18.00 in a single cell. You can now switch to a split layout where baseline and current each get their own column, with fully configurable header names — for example Avg RT (Baseline) and Avg RT (Current).

Add diff and diff % columns​

Optionally include absolute difference and percentage difference columns alongside each metric. These are grouped per metric so the table stays easy to read — all four columns for one metric sit together before the next metric begins. Column suffixes are configurable, so you can label them anything you like.

All of these settings are per-project and take effect immediately on the next report generation — no template changes required.

2. Correct Aggregation Across Multi-Node InfluxDB Setups​

Users running JMeter in a distributed setup with multiple injector nodes store results tagged by node in InfluxDB. Previously, when fetching aggregated data, PerForge did not account for the multi_node_tag field, which caused metrics to be reported per-node rather than aggregated across the whole test. This led to inflated transaction counts and incorrect throughput and response time figures in reports.

The aggregation query now correctly detects and handles the multi-node tag, summing counts across nodes and recalculating weighted averages and percentiles for the full cluster. Reports now reflect the true end-to-end test results regardless of how many injector nodes were used.

Docs Version Dropdown