-
Notifications
You must be signed in to change notification settings - Fork 815
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
Preservation of vector database #3
Comments
Comments on in the NVIDIA forum are pointing folks at https://github.com/NVIDIA/nim-anywhere which has a standalone vector database. Don't know if it preserves the data. |
@fewarren - i'm doing a little research on how the preservation should work. What are some of your requirements? |
I am not clear on what you mean by "preservation".
Fred
On Thursday, September 26, 2024 at 06:58:05 AM PDT, JT Casablanca ***@***.***> wrote:
@fewarren - i'm doing a little research on how the preservation should work.
What are some of your requirements?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
AFAIK The current project is running an in memory database. The other project is running a standalone container with a mounted file system that holds the docs. That file system is available across restarts. (I'm typing this from memory so I could be thinking of another project) |
Hi Joe,
I ran into the same problem and switched to the mounted file system approach. That solved the persistence issue. The second problem for me is that the existing Nvidia example code is extremely slow and unreliable when loading more than a few PDF files into the Milvus database. I am exploring an alternate approach that would allow for a full scale load into the database. I made some progress but then got deflected and am just now getting back to the issue. I found an example that I am trying to adapt:
GitHub - ruslanmv/How-to-load-PDF-files-into-Milvus-by-using-Spark: How to ingest and embed PDF files at scale using Spark for Retrieval Augmented Generation. We will walk through the steps required to set up the environment, install the necessary co
|
|
|
| | |
|
|
|
| |
GitHub - ruslanmv/How-to-load-PDF-files-into-Milvus-by-using-Spark: How ...
How to ingest and embed PDF files at scale using Spark for Retrieval Augmented Generation. We will walk through ...
|
|
|
It may be possible to adapt this to run locally. I am still undecided as to whether to stick with the Nvidia platform or switch totally to this alternative one. It is critical to find a fast way to load a local file based Milvus database to create a system that is usable.
I hope you make good progress towards your goals.
Fred
On Thursday, September 26, 2024 at 08:34:10 AM PDT, Joe Freeman ***@***.***> wrote:
AFAIK
The vector database holds the vectors representing the RAG documents. I don't want to have to reload the vector database (upload docs) every time I start the same project.
The current project is running an in memory database. The other project is running a standalone container with a mounted file system that holds the docs. That file system is available across restarts. (I'm typing this from memory so I could be thinking of another project)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The vector database seems to be cleared when Docker and the Nvidia AI Workbench are shutdown. Anyone know how to preserve and reload the vector database between instantiations?
The text was updated successfully, but these errors were encountered: