-
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
RAM consumption becoming bottleneck when #feature are large and RAM are intensive #4
Comments
chivee
changed the title
Use many momories when #feature is large
Use many momories when #feature is large and memory is intensive
Oct 17, 2016
yes, when RAM is intensive for your task, LightGBM will waste lots of time on paging. |
chivee
changed the title
Use many momories when #feature is large and memory is intensive
RAM consumption becoming bottleneck when #feature are large and RAM are intensive
Oct 17, 2016
chivee
added a commit
that referenced
this issue
Oct 23, 2016
add lru pool to reduce memory usage when #feature is large(#4)
eisber
pushed a commit
to eisber/LightGBM
that referenced
this issue
Mar 15, 2019
Minor readme tweaks
shiyu1994
pushed a commit
that referenced
this issue
Jul 29, 2022
feat: rough migration of acbull's source
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
LightGBM will allocate a cache to store historical histograms. This will cost about #leaf x #feature x #bin. May need to design a LRU liked cache to reduce this memory cost.
The text was updated successfully, but these errors were encountered: