Age | Commit message (Collapse) | Author |
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Results assumed all threads were used for each benchmark.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
In the future, won't have to rely on a translated string.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
For the GPU Drawing benchmark at least, it should give
some idea of the graphics capabilities of the machine.
This is the only data hardinfo currently has about that.
Maybe in the future, more advanced GPU information could
be given.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
An old PPC result from hardinfo 5.1.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* More information can be saved in benchmark.conf, while still being
compatible with older versions.
* Selecting a result give additional information about the result
and the machine the produced it.
|
|
Current CPU configurations aren't properly represented in Hardinfo.
For SMT, each hardware thread is still reported as a CPU. Clusters
with different CPU clock rates are not reported. It is common for
ARM to pair a cluster of fast cores with a cluster of slower, but
more power-efficient cores. These changes attempt to address this.
The getProcessorFrequency method now returns the processor's max
frequency for all its cores. While the new
getProcessorFrequencyDesc lists each unique frequency with a prefix
Nx with the count of cores at that freqency.
Benchmark results have been reformated to use the de-prefixed
getProcessorName and getProcessorFrequencyDesc.
As an example from benchmark.conf:
4x AMD Phenom(tm) II X4 940 Processor | 800 MHz
becomes:
AMD Phenom(tm) II X4 940 Processor | 4x 800 MHz
Which, I think, makes much more sense, as it works well with
this kind of thing:
Qualcomm Snapdragon 691 | 4x 1400 MHz + 4x 800 MHz
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
|