Skip to content

Introduce scientific notation for counters in console #818

@MuAlphaOmegaEpsilon

Description

@MuAlphaOmegaEpsilon

Sometimes it becomes difficult to grasp immediately the differences between benchmarked functions that have a wide variance in a given counter.
The aforementioned readability problem is due to the usage of the SI standard by default.
This one below is an example where I am dealing with different functions to approximate sine, look at the absolute error calculated for each one:
Screenshot_20190513_185727
It's not instantly obvious how much more precise the first function is, but it would be using scientific notation:
Screenshot_20190513_202852

The usage might be as easy as:

state.counters["Foo"] = Counter(fooVal, benchmark::Counter::kScientificNotation);

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions