-
Notifications
You must be signed in to change notification settings - Fork 167
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
Timeout issue with Milvus #333
Comments
@mattbloke99 PR: #332 increased the optimized time limit, you can update the vdbbench to v0.0.10. |
I am also getting this timeout issue with v0.0.11 trying to run Search Performance Test (1M Dataset, 768 Dims), and 10M and 100M as well. Trying to run a test using DiskANN with search_list = 100. Bare Metal Hardware:
|
I also have noticed that I do not exhibit this behavior when switching back to v0.0.7 of vectordb-bench on the exact same hardware / OS:
|
@mattbloke99 @anrahman4 Your machine needs 2400.126074722997 seconds to load + index the dataset in 0.0.7. We changed the process in the latest vdbbench, the index part is moved into optimize. Just change this We'll check if the older timeout config still works for the latest milvus cases and ajust it accordingly. AFAIK, in our 16c64G tests it costs around 1500s. |
Can confirm this worked with v0.0.11, thank you very much! |
@1191510903 8hours is a really long time. Could you please upload logs of Milvus so that I can know why this is taking so much time? Also I'd like to ask some quick questions:
|
Getting consistent timeout issues when testing Milvus with standard Cohere 1M vectors, 768 dimensions test
On c5a.8xlarge EC2 instance 32vCPU and 64Gb RAM and 128Gb SSD
The text was updated successfully, but these errors were encountered: