Skip to content
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

Why don't I have a GPU_IVF_FLAT in here #35487

Closed
1 task done
gggdroa opened this issue Aug 15, 2024 · 11 comments
Closed
1 task done

Why don't I have a GPU_IVF_FLAT in here #35487

gggdroa opened this issue Aug 15, 2024 · 11 comments
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days

Comments

@gggdroa
Copy link

gggdroa commented Aug 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:    image: milvusdb/milvus:v2.4.4-gpu
- Deployment mode(standalone or cluster):standalone 
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus==2.4.4
- OS(Ubuntu or CentOS): Ubuntu 
- CPU/Memory: 
- GPU: 
- Others:

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?

image
image

@gggdroa gggdroa added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 15, 2024
@gggdroa
Copy link
Author

gggdroa commented Aug 15, 2024

Query speed is slow how to optimize?
dim:1024; Data volume:110
use:GPU_IVF_FLAT "nlist": 5
search:"params": {"nprobe": 3}

@gggdroa
Copy link
Author

gggdroa commented Aug 15, 2024

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

@xiaofan-luan
Copy link
Collaborator

if you have low latency requirment, we would recommend you to try Cagra index

@gggdroa
Copy link
Author

gggdroa commented Aug 16, 2024

if you have low latency requirment, we would recommend you to try Cagra index

Is the latency requirement a delay for adding data?

@gggdroa
Copy link
Author

gggdroa commented Aug 16, 2024

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

@xiaofan-luan
Copy link
Collaborator

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

@yanliang567 yanliang567 removed their assignment Aug 19, 2024
@gggdroa
Copy link
Author

gggdroa commented Aug 20, 2024

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 ?

@xiaofan-luan
Copy link
Collaborator

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

@gggdroa
Copy link
Author

gggdroa commented Sep 2, 2024

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.

@xiaofan-luan
Copy link
Collaborator

by default it's 3 seconds but you can tune it

Copy link

stale bot commented Nov 9, 2024

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.

@stale stale bot added the stale indicates no udpates for 30 days label Nov 9, 2024
@stale stale bot closed this as completed Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days
Projects
None yet
Development

No branches or pull requests

3 participants