How do you troubleshoot inconsistent response times across distributed JMeter load generators?

First rule out hardware and network heterogeneity between load generator machines: confirm each agent has comparable CPU, memory, and network bandwidth, and check whether any agent is geographically farther from the system under test, since network latency differences alone can produce a consistent skew in that agent's reported response times.

Check for clock synchronization issues across agents, since if timestamps used in reporting or correlation logic aren't consistent across machines, aggregated results merged at the master can appear to show timing inconsistencies that are actually just a clock-drift artifact rather than a real performance difference.

Verify each agent is running the same JMeter version, Java version, and an identical copy of the test plan and any supporting files (like CSV data), since even small version or configuration differences between agents can produce subtly different behavior that shows up as inconsistent results when aggregated.

Check whether the agents are resource-constrained differently during the actual run - one agent hitting its own CPU or memory ceiling while generating load would itself become a bottleneck, producing artificially worse response times that reflect that agent's own saturation rather than the system under test's real performance.

Finally, confirm the master isn't introducing its own bottleneck while aggregating results from all agents in real time, since a master struggling to collect and process data from many agents simultaneously can itself skew reported timing, which is one more reason to prefer minimal listener overhead during distributed runs specifically.