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

DeviceQuantileDMatrix Improvements #6335

Closed
jamescolless opened this issue Nov 2, 2020 · 3 comments
Closed

DeviceQuantileDMatrix Improvements #6335

jamescolless opened this issue Nov 2, 2020 · 3 comments

Comments

@jamescolless
Copy link

When training on large amounts of data using a gpu the DeviceQuantileDMatrix is extremely useful in helping to avoid memory issues. In such situations it is however quite unfortunate that it is limited to 2^31-1000 elements (e.g. it cannot handle 10 million samples with 250 features). Is there any way this limitation might be removed?

Similarly it would be great if DeviceQuantileDMatrix was able to be used during external memory training (it seems as if only DMatrix is currently supported).

@hcho3
Copy link
Collaborator

hcho3 commented Nov 2, 2020

The Thrust library (a dependency of XGBoost) currently has an integer overflow bug that prevents us from creating DeviceQuantileDMatrix that's larger than 2^31 elements. See #6228. To enable DeviceQuantileDMatrix larger than 2^31 elements, the integer overflow bug in Thrust needs to be fixed.

@jamescolless
Copy link
Author

I see, thanks! Hopefully that gets resolved soon.

@hcho3
Copy link
Collaborator

hcho3 commented Nov 3, 2020

Will be fixed in #6234

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

3 participants