-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
Why is machine loading rounded? #484
Comments
@domenkozar might have figured it out:
|
Yes, IIRC that was the reason. (Looks like the C++ rewrite of build-remote got rid of the rounding BTW, which may be by accident.) |
Would it be more appropriate to divide with max jobs? I've patched our local hydra to be a bit fairer in case anyone's interested :) |
I have simply removed the That said, my build machines don't do many S3 downloads as I compile everything from source, so I don't have to worry about that. |
It is back to being floats! |
This is interesting and perhaps should be pursued anyways. |
I don't understand. Wasn't this issue about the rounding, which causes the load to be distributed unevenly across the remote machines? Based on the current code: hydra/src/hydra-queue-runner/dispatcher.cc Lines 234 to 235 in b3e0d9a
... isn't rounding still being performed, or what am I missing? |
https://github.com/NixOS/hydra/blob/master/src/hydra-queue-runner/dispatcher.cc#L131-L132
In the comparison for machine selection:
This doesn't seem necessary, and leads to incorrect results when the machines have a high speedFactor.
The text was updated successfully, but these errors were encountered: