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
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.
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
The text was updated successfully, but these errors were encountered: