-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] human readable name of benchmark #1006
Comments
DiegoKrupitza
added a commit
to DiegoKrupitza/google-benchmark
that referenced
this issue
Jun 7, 2023
Allows used to add a command line flag called `--benchmark_human_readable`. By adding this flag the arguments passed to benchmarks are formated in a human friendly format. This means that numbers that are the power of 2 are formatted as `2^x` (e.g., 64 will be `2^6`). For numbers that are the power of 10 a different formatting style is used. Numbers 0-999 no formatting is used. For numbers 1000-999999 the format `k` is used (e.g., `32000` -> `32k`). This also works for millions and billions. For numbers greater than 999 billion no special formatting is used. The design is rather simple allowing to by easily extendable. Closes: google#1006
DiegoKrupitza
added a commit
to DiegoKrupitza/google-benchmark
that referenced
this issue
Jun 19, 2023
Allows used to add a command line flag called `--benchmark_human_readable`. By adding this flag the arguments passed to benchmarks are formatted in a human friendly format. This means that numbers that are the power of 2 are formatted as `2^x` (e.g., 64 will be `2^6`). For numbers that are the power of 10 a different formatting style is used. Numbers 0-999 no formatting is used. For numbers 1000-999999 the format `k` is used (e.g., `32000` -> `32k`). This also works for millions, billions, trillions, ... For numbers greater than septillions no special formatting is used. The design is rather simple allowing to by easily extendable. Closes: google#1006
DiegoKrupitza
added a commit
to DiegoKrupitza/google-benchmark
that referenced
this issue
Jun 20, 2023
Allows used to add a command line flag called `--benchmark_human_readable`. By adding this flag the arguments passed to benchmarks are formatted in a human friendly format. This means that numbers that are the power of 2 are formatted as `2^x` (e.g., 64 will be `2^6`). For numbers that are the power of 10 a different formatting style is used. Numbers 0-999 no formatting is used. For numbers 1000-999999 the format `k` is used (e.g., `32000` -> `32k`). This also works for millions, billions, trillions, ... For numbers greater than septillions no special formatting is used. The design is rather simple allowing to by easily extendable. Closes: google#1006
DiegoKrupitza
added a commit
to DiegoKrupitza/google-benchmark
that referenced
this issue
Jun 20, 2023
Allows used to add a command line flag called `--benchmark_human_readable`. By adding this flag the arguments passed to benchmarks are formatted in a human friendly format. This means that numbers that are the power of 2 are formatted as `2^x` (e.g., 64 will be `2^6`). For numbers that are the power of 10 a different formatting style is used. Numbers 0-999 no formatting is used. For numbers 1000-999999 the format `k` is used (e.g., `32000` -> `32k`). This also works for millions, billions, trillions, ... For numbers greater than septillions no special formatting is used. The design is rather simple allowing to by easily extendable. Closes: google#1006
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/google/benchmark#running-a-subset-of-benchmarks
As shown in the readme.md,
https://github.com/google/benchmark/blame/master/README.md#L424
The benchmark name contains the state.range values as human readable format. (eg.
32k
)But the current code does not provide any switches or automatic way to format these numbers to human readable format.
Describe the solution you'd like
Provide a function to enable human readable names for benchmark names.
for powers of 2 and powers of 10.
The text was updated successfully, but these errors were encountered: