Please share the technical limitation of Caliper that you encountered.
Is there a way to set the latency unit to milliseconds instead of seconds in report.html? Sometimes, the latency is too small, perhaps counting as 0.00 seconds. So, I think there should be support for smaller units of measure in the report, e.g., milliseconds.
Please detail your feature idea that could alleviate the limitation.
It can be implemented as a configurable option in the benchmark config file.
Please share some details about your use case if possible, and how the new feature would make Caliper a better performance benchmarking framework.
No response
Please share any suggestions about the new feature's code/configuration API (using formatted YAML segments or pseudo-code).
Please share the technical limitation of Caliper that you encountered.
Is there a way to set the latency unit to milliseconds instead of seconds in report.html? Sometimes, the latency is too small, perhaps counting as 0.00 seconds. So, I think there should be support for smaller units of measure in the report, e.g., milliseconds.
Please detail your feature idea that could alleviate the limitation.
It can be implemented as a configurable option in the benchmark config file.
Please share some details about your use case if possible, and how the new feature would make Caliper a better performance benchmarking framework.
No response
Please share any suggestions about the new feature's code/configuration API (using formatted YAML segments or pseudo-code).
No response