Open gggdroa opened 3 months ago
Query speed is slow how to optimize? dim:1024; Data volume:110 use:GPU_IVF_FLAT "nlist": 5 search:"params": {"nprobe": 3}
Query speed is slow how to optimize? dim:1024; Data volume:110 use:GPU_IVF_FLAT "nlist": 5 search:"params": {"nprobe": 3}
Query time 0.3 seconds
if you have low latency requirment, we would recommend you to try Cagra index
if you have low latency requirment, we would recommend you to try Cagra index
Is the latency requirement a delay for adding data?
if you have low latency requirment, we would recommend you to try Cagra index
Is it a configuration problem? The server is not as fast as the local computer?GPU_IVF_FLAT is also used; Query time 0.07 seconds
70 ms not seems to be really slow. What is the expectation. As far as I know, fastest GPU index takes 10-20 ms. HNSW could be faster if only latency is taken into consideration. But GPU is definitely much better on throughput
70 ms not seems to be really slow. What is the expectation. As far as I know, fastest GPU index takes 10-20 ms. HNSW could be faster if only latency is taken into consideration. But GPU is definitely much better on throughput
Modified parameter: Query time 0.002s
Which is better in terms of concurrency performance, connections or Milvusclient? connections ?
70 ms not seems to be really slow. What is the expectation. As far as I know, fastest GPU index takes 10-20 ms. HNSW could be faster if only latency is taken into consideration. But GPU is definitely much better on throughput
Modified parameter: Query time 0.002s
Which is better in terms of concurrency performance, connections or Milvusclient? connections ?
I think it's kind like similar. I want to migrate from connections to milvusClient becasue it's sort of easier to understand
70 ms not seems to be really slow. What is the expectation. As far as I know, fastest GPU index takes 10-20 ms. HNSW could be faster if only latency is taken into consideration. But GPU is definitely much better on throughput
Modified parameter: Query time 0.002s Which is better in terms of concurrency performance, connections or Milvusclient? connections ?
I think it's kind like similar. I want to migrate from connections to milvusClient becasue it's sort of easier to understand
How long is the viewable time Bounded? It's been in there for a while.
by default it's 3 seconds but you can tune it
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
Is there an existing issue for this?
Environment
Current Behavior
1.GPU_IVF_FLAT cannot be used 2.How to optimize query speed
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?