Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.

NextK can be made faster #500

Open
parikg opened this issue Dec 20, 2018 · 0 comments
Open

NextK can be made faster #500

parikg opened this issue Dec 20, 2018 · 0 comments

Comments

@parikg
Copy link
Contributor

parikg commented Dec 20, 2018

Currently NextK uses RBTreeMap. This probably takes O(log N) for membership and finding max. We can replace it with a hashmap + priority queue, which will reduce membership time to O(1).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@parikg