-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Possible GPU memory usage increase. #5285
Comments
I will investigate it further later. Haven't confirmed yet. |
Keep me posted. Are you using sampling anywhere? |
Nope. Just normal benchmarking. |
I went through the PR again, I don't see any place allocating more GPU memory. In fact, we should use slightly less memory since the gradient pairs are no longer duplicated. Strange... |
Don't worry. I will look into it later. Will keep you posted. |
@RAMitchell I found the new device sketching uses more memory than the old one even after b745b7a. So before the rewrite of device sketching running mortage 1 year with dask:
After:
|
Its designed to use up to 80% memory with going OOM. Using more memory can be a good thing as it runs faster. Its only a problem if it goes OOM right? |
It seems #5093 has some impact on GPU memory usage. After the commit I encountered an OOM error on mortgage with 4 Tesla V100 16GB. @rongou
My benchmark script: https://github.com/trivialfis/dxgb_bench .
The text was updated successfully, but these errors were encountered: