DO NOT REPLY [Bug 52194] New: ab "Transfer rate" unit incorrect

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52194

             Bug #: 52194
           Summary: ab "Transfer rate" unit incorrect
           Product: Apache httpd-2
           Version: 2.2.17
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: support
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: kurienmatheww@gmail.com
    Classification: Unclassified


Here is a sample output from ab

Concurrency Level:      2
Time taken for tests:   30.782 seconds
Complete requests:      200
Failed requests:        0
Write errors:           0
Total transferred:      325644800 bytes
HTML transferred:       325578400 bytes
Requests per second:    6.50 [#/sec] (mean)
Time per request:       307.824 [ms] (mean)
Time per request:       153.912 [ms] (mean, across all concurrent requests)
Transfer rate:          10331.00 [Kbytes/sec] received

The "Transfer rate" is reported in KB/s but the computation seems to imply
KiB/s

325644800/30.782/1024 = 10331.12 KiB/s
325644800/30.782/1000 = 10579.07 KB/s

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org

[Bug 52194] ab "Transfer rate" unit incorrect

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52194

Daniel Gruno <hu...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Daniel Gruno <hu...@apache.org> ---
I'm closing this as a wontfix. First of all, whether it's KB or KiB is a moot
point, since KB is just as widely accepted as meaning 1024 as it is meaning
1000, if not more so. Secondly, this could break a lot of other programs
depending on the output being displayed as [Kbytes/sec], so fixing, what could
be considered a cosmetic "discrepancy" at best, could have serious
ramifications, and thus we're not going to do that.

-- 
You are receiving this mail because:
You are the assignee for the bug.