Skip to content
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

build.sh spawns too many jobs #5

Open
Janno opened this issue Mar 13, 2017 · 1 comment
Open

build.sh spawns too many jobs #5

Janno opened this issue Mar 13, 2017 · 1 comment

Comments

@Janno
Copy link

Janno commented Mar 13, 2017

Currently, make is called with -j, which will spawn as many jobs as there are parallel targets at any given time. On systems with (only) 4 CPUs, this leads to unnecessary contention from the ~8 jobs running simultaneously. Additionally, the memory usage far exceeds my modest 8GB of RAM.

I don't quite know how to make an optional -jN parameter work well with your build.sh setup. In any case, I think it would be safer to not use -j by default.

@jeehoonkang
Copy link
Contributor

It would be better for build.sh to accept the num_jobs parameter, e.g. ./build.sh 3 spawns three parallel jobs. It will not be super-hard, though I don't have domain knowledge on shell scripting.. In the mean time you can copy-and-paste build.sh into build-single.sh and then edit it ;)

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

No branches or pull requests

2 participants