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

feat: ScaNN index #20

Open
Tracked by #17
gaocegege opened this issue May 10, 2023 · 4 comments
Open
Tracked by #17

feat: ScaNN index #20

gaocegege opened this issue May 10, 2023 · 4 comments

Comments

@gaocegege
Copy link
Member

No description provided.

@karajan1001
Copy link

I'll take this.

@VoVAllen
Copy link
Member

@karajan1001 ScaNN might be hard to implement since original code highly coupled with tensorflow. I would suggest DiskANN, since it's designed for disk workload, which is suitable for postgres. And it's also adapted by Milvus.

@karajan1001
Copy link

karajan1001 commented May 30, 2023

@karajan1001 ScaNN might be hard to implement since original code highly coupled with tensorflow. I would suggest DiskANN, since it's designed for disk workload, which is suitable for postgres. And it's also adapted by Milvus.

Yes, I had looked into their paper and source code and noticed that it's highly coupled with TensorFlow. So it's hard to say how much performance is gotten from the algorithm and how much is gotten from the TensorFlow optimization. I was just about to ask if implementing a ScaNN without the TensorFlow optimization would be a good choice.

@gaocegege
Copy link
Member Author

https://services.google.com/fh/files/misc/scann_for_alloydb_whitepaper.pdf

Here is a whitepaper for SCANN in AlloyDB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants