Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Hard reboot itscrd70 and re-validate performances #180

Closed
valassi opened this issue Apr 25, 2021 · 1 comment
Closed

Hard reboot itscrd70 and re-validate performances #180

valassi opened this issue Apr 25, 2021 · 1 comment
Assignees
Labels
performance How fast is it? Make it go faster!

Comments

@valassi
Copy link
Member

valassi commented Apr 25, 2021

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.

@valassi
Copy link
Member Author

valassi commented Apr 30, 2021

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.

@valassi valassi closed this as completed Apr 30, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
performance How fast is it? Make it go faster!
Projects
None yet
Development

No branches or pull requests

1 participant