-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[Question]: Why indexing so slow? #13313
Comments
To address the issue of 0% GPU utilization during the indexing process with your NVIDIA A40 GPU, follow these targeted steps:
This approach focuses on ensuring compatibility and proper configuration for GPU utilization, leveraging specific classes designed for NVIDIA GPUs, and monitoring to confirm active GPU engagement.
|
50GB of data is a ton of data to load into memory. I wonder if it's getting stuck there? If you hit ctrl+c, the traceback would tell us where it is in the code. I would also suggest testing the embedding model on its own first to ensure it uses GPU If you have the memory, you can also increase the batch size: |
Also, by specifying |
You also didn't specify a vector DB, so all the embeddings (50GB of text of embeddings!!) will be in memory -- probably also not ideal |
If I was to re-write this, it might look like:
|
Thanks for ur help, really apperciate it. I realized it was stuck and split it into small batches then. thanks a lot. |
Question Validation
Question
I'm trying to create indexes for a database that is 50 GB in size, and I've spent more than 5 days running the code below without any results. Then I noticed that the GPU utilization remains at 0; what should I do to speed up the indexing process?
The text was updated successfully, but these errors were encountered: