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

Initial pool size should not be hard coded #14760

Open
harrism opened this issue Jan 15, 2024 · 0 comments
Open

Initial pool size should not be hard coded #14760

harrism opened this issue Jan 15, 2024 · 0 comments
Labels
feature request New feature or request

Comments

@harrism
Copy link
Member

harrism commented Jan 15, 2024

Now that rmm::pool_memory_resource does not by default use half of available memory for the initial pool size, cuDF has hard-coded 50% of free memory as the initial size to match previous behavior for benchmarks and tests. This should be configured globally somewhere.

         I'm thinking about whether we should parse `percent_of_free_device_memory` from some env variable, instead of hard coding like this in many places. By doing so we can control the number we want at runtime.

Originally posted by @ttnghia in #14741 (comment)

@harrism harrism added the feature request New feature or request label Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Status: TODO
Development

No branches or pull requests

1 participant