This repository has been archived by the owner on Jan 13, 2022. It is now read-only.
add wait for message queue to drain before final siege #88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For older Aarch64 hosts the /warmup-status message is not sufficient to determine
that the server is warmed up and ready to collect benchmarking numbers. The longer
running benchmarks may still have a number of messages still waiting in the queue.
This change adds another wait loop before the final siege to make sure the queue is
empty and new requests will go through the JIT after the retranslateAll.
(Yes, this showed up with toys-fibonacci if you were curious)