Repository navigation
Conversation
Measured live, a piece takes 15 to 20 s from a Worker and deliveries come about every three minutes, so a 30 s budget moved one or two pieces a clip per delivery: about 2 MB/s a clip. 60 s moves three or four. The cost is a longer step holding the platform queue's batch.
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Measured on a live run: a 200 MiB piece takes 15 to 20 s from a Worker (10 to 14 MB/s), and deliveries come about every three minutes (the queue books to the minute and sweeps each minute). A 30 s budget moved one or two pieces per clip per delivery, about 2 MB/s a clip: two 15 GB files took about two hours.
RELAY_BUDGET_MSgoes to 60 s, so a delivery moves three or four pieces per clip.Typecheck clean, 185 unit tests, end to end ALL OK.