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
Something I noticed is that current GHA workflows simply call make - which defaults to running the jobs sequentially. Meanwhile, GitHub's public runners have more than one CPU core.
Your builds could probably be significantly sped up by changing the make call to something like make -j4, or more universally make -j $(nproc). It could also be possible to switch over to ninja (which defaults to one job per CPU thread), but I don't think it's installed by default in GHA images.
The text was updated successfully, but these errors were encountered:
Something I noticed is that current GHA workflows simply call
make
- which defaults to running the jobs sequentially. Meanwhile, GitHub's public runners have more than one CPU core.Your builds could probably be significantly sped up by changing the
make
call to something likemake -j4
, or more universallymake -j $(nproc)
. It could also be possible to switch over to ninja (which defaults to one job per CPU thread), but I don't think it's installed by default in GHA images.The text was updated successfully, but these errors were encountered: