Closed kiran94 closed 3 years ago
vegeta report -type=json
emits durations always in nanoseconds (machine readable).
vegeta report
emits durations in human readable units (micro-second, milli-second,second,...)
https://github.com/tsenart/vegeta/blob/master/README.md#report--typejson
@surenderssm Happy to close this if you feel that it's the users responsibility to take the machine readable output from when json
is set to human readable and it shouldn't be an additional flag.
Thanks
Looks like yes to me. @tsenart any other thoughts ?
I'm not sure if this is intentional but feel free to close if so!
Yep, it's intentional. We don't want to loose precision in the JSON report since it's not for direct human consumption, unlike the text report.
Version and Runtime
Expected Behaviour
Values in the JSON Report to be be consistent with the normal report
Actual Behaviour
Decimal place is dropped
Steps to Reproduce
Run an Attack to generate some results
Create a normal report:
cat output\is_available_all_found_.bin | vegeta report
Create a JSON report
cat output\is_available_all_found_.bin | vegeta report -type json
Take mean latency for example, in the normal report it is
110.717ms
and in the JSON report it is110717316
so the decimal place was dropped but I would have expected both reports to be consistent in units. I'm not sure if this is intentional but feel free to close if so!Additional Context
N/A