Bug 57679 - Summary Report # Samples counter rolls over and causes miscalculated fields for long running tests with high throughput
Summary: Summary Report # Samples counter rolls over and causes miscalculated fields f...
Status: NEEDINFO
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.12
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-09 13:05 UTC by Ryan Whitworth
Modified: 2015-03-12 21:08 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Whitworth 2015-03-09 13:05:25 UTC
On the Summary Report listener page the # Samples field can roll over to zero during a long running test.  This roll over then affects the values in the other fields that are calculated based on running time and the # of samples (average, throughput, KB/sec, etc).

This roll over happened during a 3 day test (over a weekend) when the throughput was roughly 35,000 connections a second.  It looks as though the # Samples field is kept as a 32-bit number.  Could this be increased to a 64-bit number so that longer tests could be run without fear of the averages becoming inaccurate?
Comment 1 Philippe Mouawad 2015-03-09 21:01:27 UTC
Hi,
Thanks for report.
Nice to know you reach 35000 connections per second !
I would be very interested to know a bit more about your use case if possible.

Regarding the bug, we are currently in release process of 2.13 which should be out soon, so we will try to handle this one in next release.

Regards