https://bz.apache.org/bugzilla/show_bug.cgi?id=60278
Philippe Mouawad <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |[email protected] | |om --- Comment #1 from Philippe Mouawad <[email protected]> --- (In reply to Milamber from comment #0) > Try to open a aggregate report saved into a file with the Aggregate listener. > > With 2.12 : > sampler_label,aggregate_report_count,average,aggregate_report_median, > aggregate_report_90%_line,aggregate_report_min,aggregate_report_max, > aggregate_report_error%,aggregate_report_rate,aggregate_report_bandwidth > SAMPLER1,204,82434,76089,129444,1159,208015,0.09313725490196079,0. > 03735365469805521,21.15778783560153 > > With nightly (and 2.13, 3.0) : > Label,# Samples,Average,Median,90% Line,95% Line,99% Line,Min,Max,Error > %,Throughput,Received KB/sec,Sent KB/sec > SAMPLER1,204,82434,76089,129444,145355,177257,1159,208015,9.31%,.0,21.16,0.00 > > The %Error value : > 0.09313725490196079 --> 9.31% (lost precision) > > The Rate value: > 0.03735365469805521 --> .0 (lost value!) > > The bandwidth value: > 21.15778783560153 -->21.16 (lost precision) > > The new Sent KB value will probably lost precision too. > > The bugzilla https://bz.apache.org/bugzilla/show_bug.cgi?id=57514 are the > source of theses issues, with the FORMATS array inside the > SummaryReport.java. Hi Milamber, The export makes some rounding. It doesn't hurt me except for the Rate value. We could increase the number of decimals by 1 or 2. What do you think ? Thanks -- You are receiving this mail because: You are the assignee for the bug.
