-
Notifications
You must be signed in to change notification settings - Fork 912
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
[FEA] Replace cudf's concurrent_unordered_map
with cuco::static_map
.
#10401
Comments
@bdice Minor correction: |
This issue has been labeled |
The `concurrent_unordered_multimap` is no longer used in libcudf. It has been replaced by `cuco::static_multimap`. The majority of the refactoring was done in PRs #8934 and #9704. A similar effort is in progress for `concurrent_unordered_map` and `cuco::static_map` in #9666 (and may depend on porting some optimizations from libcudf to cuco -- need to look into this before doing a direct replacement). This partially resolves issue #10401. cc: @PointKernel @vyasr Authors: - Bradley Dice (https://github.com/bdice) Approvers: - Yunsong Wang (https://github.com/PointKernel) - Vyas Ramasubramani (https://github.com/vyasr) - Jake Hemstad (https://github.com/jrhemstad) URL: #10642
This issue has been labeled |
Closing this in favor of #12261 |
I noticed that
concurrent_unordered_map
andconcurrent_unordered_multimap
are not defined in thecudf
namespace (they're in the global/root namespace). After discussion with @PointKernel, it seems we may be able to replace the existing uses ofconcurrent_unordered_map
withcuco::static_map
and delete these from libcudf. I plan to look at this after finishing another refactoring project #10081. Currentlycuco
only supports keys/values up to 8 bytes, but these use cases appear to be fine even with that limitation.Current uses of
concurrent_unordered_map
:Current uses ofconcurrent_unordered_multimap
:None. Only tests. https://github.com/rapidsai/cudf/blob/b3dc9d6adf16635c94a1735ad9ca73c12494884e/cpp/tests/hash_map/multimap_test.cuThe text was updated successfully, but these errors were encountered: