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

Increasing the number of CPUs to build R packages #580

Closed
betatim opened this issue Feb 16, 2019 · 2 comments
Closed

Increasing the number of CPUs to build R packages #580

betatim opened this issue Feb 16, 2019 · 2 comments

Comments

@betatim
Copy link
Member

betatim commented Feb 16, 2019

via #1240:

We could set the number of CPUs used during the building of R packages to >1 to get a speed up. However I am not sure how we would automatically determine what number to set this to. I think counting the number of cores from inside a container will give you the number of cores on the host which you might or might not be able to use. When running on k8s it would be even trickier because the resources are limited via the pod config.

My assumption is that running with a configuration of (say) ncpus=16 when really you can only use 2 cores will slow things down even more than running with ncpus=1 does.

Maybe in connection with jupyterhub/binderhub#579 we can set it when we know what the user set the limit to?

related: jupyterhub/binderhub#412

@choldgraf
Copy link
Member

mmmm I don't know that much about how to check for the CPU power available and request something different depending on what's returned. This feels like it'd be pretty tricky to debug or maintain, no?

@choldgraf
Copy link
Member

@betatim how do you feel about this one? dontfix? Or worth discussing more?

@betatim betatim closed this as completed Apr 27, 2019
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