google
JSON files report both CPU time and real time
Each benchmark has a preference for real time or CPU time, depending on what's being tested, but gbenchmark always stores both values in JSON output files. This means it's not possible to programmatically determine, when reading a JSON file, whether CPU time or real time is relevant in a particular benchmark.
It seems that when the benchmark declares a preference for real time, I could parse the benchmark name for the string /real_time. But that seems hackish...
Each benchmark has a preference for real time or CPU time, depending on what's being tested, but gbenchmark always stores both values in JSON output files.
It displays both in the console, too. This is very intentional.
This means it's not possible to programmatically determine, when reading a JSON file, whether CPU time or real time is relevant in a particular benchmark.
It seems that when the benchmark declares a preference for real time, I could parse the benchmark name for the string
/real_time. But that seems hackish...
Yeah, i guess that is the (current) way. What is the use case, why do you want to know that after the benchmark?
What is the use case, why do you want to know that after the benchmark?
Because we're going to inject benchmark results in a database and then track results across time, try to detect regressions, etc. For that we need to know which number is authoritative for each benchmark.