-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
LightGBM GPU requires folder permission to compile kernels #2955
Comments
It seems the compute cache path is hard coded to use the If you have permission on this machine, I think you can create a symbolic link from |
I see |
To make it more flexible, we can check for an environment variable (something like I am not sure about the status of boost/compute, but I feel it has not been abandoned yet (last commit was less than 1 year ago on the |
I like the idea! Speaking about the status, indeed, it is not abandoned officially. But last commit in Also, |
|
Closed in favor of being in #2302. We decided to keep all feature requests in one place. Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature. |
This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Duplicate issue (but closed): #1531
Environment info
Operating System: Ubuntu 18.04
CPU/GPU model: Intel Quad Xeon Platinum 8280 / custom NVIDIA GPU
C++/Python/R version: R 4.0 (devel), Python 3.8, gcc-7.4.0
LightGBM version or commit hash: 03ce02a
Error message
Reproducible examples
User must not have compiled any kernel before usage of LightGBM GPU.
Example in R:
Steps to reproduce
Solutions proposed:
Temporary solutions:
BOOST_COMPUTE_USE_OFFLINE_CACHE=0
but incur warmup penalty of kernel every time a model is trained (not recommended for HPC users, because 100k models with 1 second of compilation means 100 seconds wasted)Maybe @huanzhang12 has a better recommendation to solve this in environments where writing under
~/.boost_compute
is not allowed.The text was updated successfully, but these errors were encountered: