-
Notifications
You must be signed in to change notification settings - Fork 6
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
Tasti engine #50
Tasti engine #50
Conversation
…lass to keep old cluster representatives
…ating proxy scores.
# Conflicts: # aidb/engine/base_engine.py
# Conflicts: # aidb/query/query.py # aidb/utils/constants.py # aidb/vector_database/chroma_vector_database.py # aidb/vector_database/faiss_vector_database.py # aidb/vector_database/tasti.py # aidb/vector_database/vector_database.py # aidb/vector_database/weaviate_vector_database.py # tests/tasti_test/tasti_test.py
Could you review this branch? @ddkang |
I think part of the reason this PR is a bit confusing to review is that it isn't connected to any downstream query. I think it would be best to merge this with an example of a downstream query optimization. I think there are a few options:
What do you think? @ttt-77 |
Yes, when I was writing this PR, I was not so clear about what should be return from TASTI engine and how it can be combined better with specific query. I checked previous AIDB code and TASTI paper many times. I think in previous code, the proxy scores are only used to order the inference service. Maybe I am missing something. I will consider the first and second options and determine whether any changes need to be made to the current PR |
And maybe I can also add a design document in Wiki page? |
A design doc sounds good. I'd like to see an actual implementation of 1, 2, or 3 in this PR, otherwise it's a bit hard to tell. |
I will do that |
@ddkang Could you please review the new commit? And here is the design document, https://github.com/ddkang/aidb-new/wiki/TASTI-Engine-%E2%80%90-Design-Document |
This PR is ready for review @ddkang |
@ttt-77 Just to be sure that the proxy score implementation and all is correct. I would also suggest that you compare the number of inference service calls for limit queries with these proxy scores and some adversarial proxy score (maybe you can test with (1 - proxy_score)). If the implementation is correct, number of inference service calls will be fewer in case of perfect proxy scores. |
Currently, the embedding in vector database are generated randomly. I think we can't test it now. Could you please move your suggestion to issue #54 ? We can check it later. |
Yes. We have jackson dataset with the embeddings. Surely, we can test it later. I mean from a code execution point of view, it is alright. But for proxy scores correctness etc, is there a better way to test rather than just reading code? |
No description provided.