-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Feature]: Support local disk caching and Mmap data #21866
Comments
/assign |
|
The IVF_FLAT doesn't support mmap for now, due to it stores the original data separately. Will work on it after the C++ segment loader ready |
I'm going to support IVF index with mmap as Knowhere has changed IVF impl to contain data part |
@faiss already support mmap |
Need to dive into the faiss impl and file format |
@cydrain would this index contain the vector data if it was created in old version? |
We actually have a user who want to run mmap on FLAT index |
@yah01 : does faiss also support adding metadata along with embeddings or is this only done by knowhere ? |
faiss does‘t have idea of metadata |
support enable/disable mmap for index, the user could alter the index's mode by `AlterIndex` method related: #21866 --------- Signed-off-by: yah01 <[email protected]> Signed-off-by: yah01 <[email protected]>
this supports mmap for marisa trie index related #21866 Signed-off-by: yah01 <[email protected]>
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
Now Milvus fully loaded vector index into memory to support query/search, but it required too much memory and could cause OOM if memory is not enough.
To improve, we could define load as put data into local disk, and mmap the data into memory. All memory in data will be managed by operating system page cache and user can loaded larger dataset into milvus without fully in memory (If memory is enough, I would expect similar performance compared to current in memory version).
There are few things we need to investigate before put this on our schedule:
Describe the solution you'd like.
No response
Describe an alternate solution.
No response
Anything else? (Additional Context)
No response
The text was updated successfully, but these errors were encountered: