-
Notifications
You must be signed in to change notification settings - Fork 799
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
Wasm runtime compilation is largely single-threaded #2636
Comments
What profile did you use? Release? |
Yes, standard release profile |
Clarification: it is largely single-threaded even on Linux |
#4946 there was this pr recently to ensure we are not overloading the system. |
Well, it is massively under-utilizing my system instead. On 32C64T system seeing single remaining WASM runtime blocking other crates from being compiled while using a single CPU core is a frustrating experience. It is the most pronounced for polkadot-sdk contributions where there are many crates including numerous runtimes to compile. |
Ahh now I get what you mean. These are basically pipeline blockers, forcing the compiler to wait on them to compile. When it comes to linking, compression etc it will not use multiple CPUs anymore. |
Not sure we can do that much. I mean we can probably move some crates around, but in the grand scheme I doubt that it will change something. |
I understand fundamental constraints of linking and such, but build script of runtimes takes incomparably large amount of time for some reason, there must be some low-hanging fruits there. Compiling native runtime takes a small fraction of the time. |
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
I was recompiling things on Windows many times last few days and noticed that wasm runtime build script only uses a single CPU core for some reason, slowing things down significantly.
I'm not sure why this happens, but I don't think I have seen this behavior on Linux.
This is not a priority, but maybe someone knows why this happens and can point me in the direction that will help to resolve this.
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: