You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a related to vectorisation issue #71 and to the big PR #171. In particular, it is closely related to issue #173 about AVX512.
In order to measure the processor speed for AVX512, I need a hard reboot of my reference VM to enable CPU pass through. This would more generally allow using perf in a more complete way with hardware counters. In principle, this should not change performances, but one never knows.
An alternative is to rebuild itscrd03 on centos7, with CPU passthrough. This is a downgrade of this VM from centos8, hoping thatthis is enough to address the still-not-completely-understood issue #116.
Just a reminder and a placeholder for (hopefully unnecessary) performance comparisons.
The text was updated successfully, but these errors were encountered:
Ok I have been using for a few days the new itscrd03 with CPU passthrough (rebuilt on centos7, ok no tsc issue), and it works nicely, with perf stat. So I hard rebooted itscrd70, performance is good, and perf stat is available. Can be closed.
This is a related to vectorisation issue #71 and to the big PR #171. In particular, it is closely related to issue #173 about AVX512.
In order to measure the processor speed for AVX512, I need a hard reboot of my reference VM to enable CPU pass through. This would more generally allow using perf in a more complete way with hardware counters. In principle, this should not change performances, but one never knows.
An alternative is to rebuild itscrd03 on centos7, with CPU passthrough. This is a downgrade of this VM from centos8, hoping thatthis is enough to address the still-not-completely-understood issue #116.
Just a reminder and a placeholder for (hopefully unnecessary) performance comparisons.
The text was updated successfully, but these errors were encountered: