Skip to content

Multiprocessing env disable#211

Merged
seddonym merged 2 commits intomasterfrom
multiprocessing-env-disable
Apr 24, 2025
Merged

Multiprocessing env disable#211
seddonym merged 2 commits intomasterfrom
multiprocessing-env-disable

Conversation

@seddonym
Copy link
Collaborator

@seddonym seddonym commented Apr 24, 2025

The multiprocessing doesn't seem to work reliably in all environments; also the optimization of the threshold of when to start doing it is somewhat arbitrary.

This exposes an environment variable to allow callers to control it. We imagine this will go away once import scanning is moved into Rust, hence the decision just to use an environment variable rather than add it to the method arguments.

image

@codspeed-hq
Copy link

codspeed-hq bot commented Apr 24, 2025

CodSpeed Instrumentation Performance Report

Merging #211 will not alter performance

Comparing multiprocessing-env-disable (f54b9a1) with master (d6da591)

Summary

✅ 22 untouched benchmarks

@seddonym seddonym force-pushed the multiprocessing-env-disable branch 2 times, most recently from f5ae0e0 to e3d36e5 Compare April 24, 2025 13:24
This provides the ability to adjust the arbitrary cut off, or turn off
multiprocessing altogether.
@seddonym seddonym force-pushed the multiprocessing-env-disable branch from b818cb5 to f54b9a1 Compare April 24, 2025 14:56
@seddonym seddonym marked this pull request as ready for review April 24, 2025 15:00
@seddonym seddonym merged commit dcdd226 into master Apr 24, 2025
17 checks passed
@seddonym seddonym deleted the multiprocessing-env-disable branch April 24, 2025 15:01
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.

1 participant