-
Notifications
You must be signed in to change notification settings - Fork 1k
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
More parallel tests #1255
Comments
Yep, the only parallelism we have is that one from different binaries. As you say, it's not the end of the world, but it would be good to improve this if it's a bottleneck in Core. I thought a few times about this issue, but my pain was never big enough that I actually spend time working on this.
|
This is also a pain-point for me -- with a 32-core machine, the bottlenecks in building Core are I like the idea of running |
Supporting |
@Sjors FYI if you don't actually care to run the tests in full, you can set the environment |
I checked, and I don't think there's no way to access the But yeah, we could still just use 4x16. |
When running
make -j… check
I noticed it doesn't use more than 3 CPU's at any one time, one fortests
,exhaustive_tests
andnoverify_tests
. At least when I tried it on an Intel macOS 13.2 machine.This is a bottleneck when running the full Bitcoin Core test suite on something slow like with msan (tried on a Ubuntu 22.10 x86_64 machine using Docker).
That said, it's not the end of the world either, since I could also just run more test suite (Docker containers) in parallel.
The text was updated successfully, but these errors were encountered: