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

Performance tracking issue #6

Open
1 of 4 tasks
vadixidav opened this issue Apr 29, 2019 · 1 comment
Open
1 of 4 tasks

Performance tracking issue #6

vadixidav opened this issue Apr 29, 2019 · 1 comment

Comments

@vadixidav
Copy link
Member

vadixidav commented Apr 29, 2019

Performance is currently only beating linear (which is incredibly fast on modern processors) for exact search at > 1M features. This is probably beatable, but it will require some optimizations. Below is the list of optimizations and their issues that need to be made:

k-NN

@vadixidav
Copy link
Member Author

After closing #7 I am now getting the following:

neighbors/nearest_1_hwt_maxerr_0/16777216                        
                        time:   [17.479 ms 17.687 ms 17.849 ms]

This is a reasonable speedup over linear at 2^24 features.

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

1 participant