Skip to content

Launch scheduler threads lazily #3493

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Sep 14, 2012 · 1 comment
Closed

Launch scheduler threads lazily #3493

brson opened this issue Sep 14, 2012 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Sep 14, 2012

I don't need all 64 threads on my supermicro starting up at the same time if I'm not going to use them.

Scheduler threads have 100K+ overhead currently.
@brson
Copy link
Contributor Author

brson commented Sep 14, 2012

Additionally, we might want to prefer already launched + empty threads over starting new ones.

@Blei Blei mentioned this issue Sep 14, 2012
Closed
@brson brson closed this as completed in 68e755b Sep 19, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
@topecongiro
Add a test for rust-lang#3493
788a4cb
RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 23, 2024
@bors
Auto merge of rust-lang#3493 - eduardosm:env-set, r=oli-obk
3b5d663 
Add `-Zmiri-env-set` to set environment variables without modifying the host environment

This option allows to pass environment variables to the interpreted program without needing to modify the host environment (which may have undesired effects in some cases).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson