Open lilyanatia opened 3 days ago
Hey, thanks for the report.
I disagree with your interpretation. It's not that --accurate-pp
is "wrong". If you compare the output from QEMU vs no QEMU you'll see that almost everything (except max frequency) is "wrong". And it's not wrong, it's simply QEMU tampering the values (VMs can report whatever values they want).
In particular, in this case it's the microarchitecture and the number of sockets what is making cpufetch think that the peak performance is higher, but cpufetch can do nothing about that, except maybe warning the user when running under a VM about these effects. I would expect the user to be aware of this though, that's why no warning is displayed right now.
correct output:
running in qemu-x86_64 results in 4x the TFLOP/s:
I'm not sure if it's possible to fix
--accurate-pp
under emulation other than actually running a benchmark, but perhaps a warning that "Peak Performance", even with--accurate-pp
, might be completely wrong when a hypervisor is detected would be a good idea.