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
I've had a build on me take 5h with multiple timeouts when run with 2 CPU cores due to MPI + OpenMP oversubscription. While typically it only costs 1h on 4 cores.
Suggestions:
Provide a global macro where we can define the total number of CPU cores/memory etc. that a particular .spec file requires. This could be defined only once and be independent of %if statements to keep the parsing simple.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Opening a discussion related to this copr issue.
Background:
I've had a build on me take 5h with multiple timeouts when run with 2 CPU cores due to MPI + OpenMP oversubscription. While typically it only costs 1h on 4 cores.
Suggestions:
Provide a global macro where we can define the total number of CPU cores/memory etc. that a particular
.spec
file requires. This could be defined only once and be independent of%if
statements to keep the parsing simple.Beta Was this translation helpful? Give feedback.
All reactions