Skip to content

Commit

Permalink
Bunch more aggressively, but schedule less tasks (#4465)
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
jonathanmetzman committed Jan 8, 2025
1 parent 25b1452 commit 3f87c5d
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions src/clusterfuzz/_internal/base/tasks/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -90,11 +90,11 @@
# See https://github.com/google/clusterfuzz/issues/3347 for usage
SUBQUEUE_IDENTIFIER = ':'

UTASK_QUEUE_PULL_SECONDS = 120
UTASK_QUEUE_PULL_SECONDS = 150

# The maximum number of utasks we will collect from the utask queue before
# scheduling on batch.
MAX_UTASKS = 800
MAX_UTASKS = 3000

UTASKS = {
'analyze',
Expand Down
2 changes: 1 addition & 1 deletion src/clusterfuzz/_internal/cron/schedule_fuzz.py
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ def schedule_fuzz_tasks() -> bool:
# TODO(metzman): Put the CPU-based scheduling in tworkers.
available_cpus = get_available_cpus(project, 'us-east4')
# TODO(metzman): Remove this as we move from experimental code to production.
available_cpus = min(available_cpus, 12000)
available_cpus = min(available_cpus, 3000)
fuzz_tasks = get_fuzz_tasks(available_cpus)
if not fuzz_tasks:
logs.error('No fuzz tasks found to schedule.')
Expand Down

0 comments on commit 3f87c5d

Please sign in to comment.