You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rubén Laguna (Bug 40791):
Calculator.java used by SummaryReport uses the startTime of the first sample as
start time for it's own calculations. First sample to arrive to summary report
is not always the first sample in time because some operations may have started
earlier and will arrive later because the sample come from a jmeter-server (in
distributed testing with batch mode this is noticiable) or because the time to
complete the sample locally is high.
Furthermore Calculator (and Summary Report) take the endTime of the last sample
to arrive as the endTime for all SummaryReport calculations. This is worse
because in distributed testing the time is not always synchonized to the
millisecond and the samples come in batches.
This produces inaccuracy in the calculations. I'll attach a patch to correct
this behavior. Taking the min of samples startTime and the max of the samples
endTime
Severity: normal
OS: other
The text was updated successfully, but these errors were encountered:
Rubén Laguna (migrated from Bugzilla):
Changes the way SummaryReport calculates the thoughput taking into account the
min and max of startTimes and endTimes. Previous version relies on samples
coming in order to accurately make the calculations. This assumption is false
in distributed testing (very false in batch mode!)
Created attachment calculator.diff: Calculator.java patch to take min and max of startTimes and endTimes into account
Rubén Laguna (Bug 40791):
Calculator.java used by SummaryReport uses the startTime of the first sample as
start time for it's own calculations. First sample to arrive to summary report
is not always the first sample in time because some operations may have started
earlier and will arrive later because the sample come from a jmeter-server (in
distributed testing with batch mode this is noticiable) or because the time to
complete the sample locally is high.
Furthermore Calculator (and Summary Report) take the endTime of the last sample
to arrive as the endTime for all SummaryReport calculations. This is worse
because in distributed testing the time is not always synchonized to the
millisecond and the samples come in batches.
This produces inaccuracy in the calculations. I'll attach a patch to correct
this behavior. Taking the min of samples startTime and the max of the samples
endTime
Severity: normal
OS: other
The text was updated successfully, but these errors were encountered: