-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Let arbitrator system use nano second #11415
Conversation
✅ Deploy Preview for meta-velox canceled.
|
e26f573
to
77a3b28
Compare
@tanjialiang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tanjialiang thanks for the fix and improvement!
@@ -95,28 +95,28 @@ class ArbitrationOperation { | |||
|
|||
/// Returns the remaining execution time for this operation before time out. | |||
/// If the operation has already finished, this returns zero. | |||
size_t timeoutMs() const; | |||
int64_t timeoutNs() const; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uint64_t ? shall we be consistent? I saw Timer.h use uint64_t
@tanjialiang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Some tests are flaky because current milisecond is too coarse. And some operations run sub-milisecond. We want to change it to nanosecond across the board to reduce this flakiness
@tanjialiang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@tanjialiang merged this pull request in 62b0a12. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Use nano seconds in arbitrator system to avoid flakiness in time dependent tests.