Skip to content

fix: don't run nested ProcessPoolExecutors#1008

Merged
bhearsum merged 1 commit into
taskcluster:mainfrom
bhearsum:fix-don-t-run-nested-processpo
Jul 17, 2026
Merged

fix: don't run nested ProcessPoolExecutors#1008
bhearsum merged 1 commit into
taskcluster:mainfrom
bhearsum:fix-don-t-run-nested-processpo

Conversation

@bhearsum

Copy link
Copy Markdown
Contributor

This is kindof a regression from the introduction of the ProcessPoolExecutor for taskgraph generation. It's not necessarily wrong or broken to nest these...but in graphs where memory usage is high during generation it can sometimes cause OOMs. There's really no advantage to using two levels of multiprocessing, so we should avoid doing so.

This is kindof a regression from the introduction of the ProcessPoolExecutor for taskgraph generation. It's not _necessarily_ wrong or broken to nest these...but in graphs where memory usage is high during generation it can sometimes cause OOMs. There's really no advantage to using two levels of multiprocessing, so we should avoid doing so.
@bhearsum
bhearsum marked this pull request as ready for review July 16, 2026 20:59
@bhearsum
bhearsum requested a review from a team as a code owner July 16, 2026 20:59
@bhearsum
bhearsum requested a review from jcristau July 16, 2026 20:59
@bhearsum
bhearsum merged commit f303f38 into taskcluster:main Jul 17, 2026
23 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants