-
Notifications
You must be signed in to change notification settings - Fork 564
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
Support multiple regions for schedule_fuzz_task.py #4524
Closed
Closed
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
Only do this in oss-fuzz for now.
From now on I will commit oss-fuzz work specifically to this branch. --------- Co-authored-by: Vitor Guidi <[email protected]> Co-authored-by: Ali HIJAZI <[email protected]>
Also increase the number of utasks we can get from the queue
Use randomness to "load balance" for now. --------- Co-authored-by: Vitor Guidi <[email protected]> Co-authored-by: Ali HIJAZI <[email protected]>
Scale up fuzzing on batch
1. Don't defer the tasks, they've already been deferred. 2. Improve the scheduling time by 20% by batching calls so that we only need to read YAML and query the database once, per queue read. --------- Co-authored-by: Vitor Guidi <[email protected]> Co-authored-by: Ali HIJAZI <[email protected]>
Use imap_unordered for these two improvements. 1. Async signing, we can start signing the arbitrary URLs before we are done listing and signing the existing URLs. 2. Ignoring the order means we can sign/list even faster. 3. Use of iterables means we don't need to use unnecessary memory.
We're experiencing big delays in our batch scheduling (meaning batch is an hour behind). We may have too many jobs for batch. Start trying to bunch the tasks more efficiently so we have fewer jobs.
The experiment failed because batch is throttling job creation for some reason. Lower the amount of tasks we schedule so we don't create a backlog that prevents non-fuzz tasks from being run.
It's not used anymore. Related: b/381528482
We don't use it anymore. Related: b/381528482
Allow utask_main scheduling
Also delete some example code.
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.