-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Multithreaded mode #128
Comments
I think this is a great idea. I would accept a PR to implement this. |
I thought about it, but decided that I don't have the time to do it myself. |
Hey, I was looking around and it seems that this issue hasn't been addressed in quite a long time. Wanting to know, if you are still accepting PR, for this issue. |
@NishantJoshi00 you might want to try #175 that adds a way to get a list of commands out, and then you can run those commands separately for different processes. I'm using that command to run the processes on different machines even. |
Interesting! I was able to come up with a similar solution for improving performance. I achieved parallelization with |
This feature request is no longer as important as it was when I filed it, because rust 1.64.0 supports multitarget builds. So you can now do something like |
Yeah, this is still useful and PR is welcome. |
--each-feature and --feature-powerset are great! My only complaint is that they are slow. bpytop shows that I'm never using more than one core when running cargo-hack. It would be awesome if cargo hack could run multiple cargo processes in parallel, one for each feature combination. Normally Cargo doesn't allow two processes to share the same build directory at the same time, so you could set
CARGO_TARGET_DIR
to a separate value for each.There is a little contention for the crate cache, but my crude benchmark shows that I can build targets in parallel in about a quarter of the time it takes to build them sequentially.
The text was updated successfully, but these errors were encountered: