Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Actions: Use Intel OneAPI compiler to avoid needing custom runners #227

Closed
conradtchan opened this issue Feb 11, 2022 · 1 comment · Fixed by #228
Closed

Actions: Use Intel OneAPI compiler to avoid needing custom runners #227

conradtchan opened this issue Feb 11, 2022 · 1 comment · Fixed by #228

Comments

@conradtchan
Copy link
Collaborator

As mentioned in #224, the build with SYSTEM=ifort is slow, even with parallelised builds, because there are only 4 custom runners. The maximum speedup from parallelisation is 4x, and during busy times there is a long backlog. This slows down the development workflow.

Intel's compilers are now free for academic use.

Instructions for using ifort in github actions: https://neelravi.com/post/oneapi-github-workflow/

Workflows requiring ifort can be run on github's runners (and thus on forks). The benchmarks should still be run on the custom runners because consistent system hardware and dedicated CPU cores are required for timing.

@conradtchan conradtchan changed the title Use Intel OneAPI compiler to avoid needing custom runners Actions: Use Intel OneAPI compiler to avoid needing custom runners Feb 11, 2022
@danieljprice
Copy link
Owner

awesome :)

conradtchan added a commit that referenced this issue Feb 14, 2022
Intel compilers can be installed onto github runners for free, so:

Test and build workflows are now run on github runners to reduce the demand on custom runners. Benchmarks are still run on custom runners.
Workflows requiring intel compilers can now run on forks.
Resolves Actions: Use Intel OneAPI compiler to avoid needing custom runners #227

Testing:
Full test suite

Did you run the bots? no - not required
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants