milvus
milvus copied to clipboard
[Bug]: [benchmark][cluster]kafka has a higher latency than pulsar in the search, query, load interface
Is there an existing issue for this?
- [X] I have searched the existing issues
Environment
- Milvus version:
- Deployment mode(standalone or cluster):cluster
- SDK version(e.g. pymilvus v2.0.0rc2):pymilvus 2.1.0dev87
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
Current Behavior
argo test-etcd-no-clean-trj4s-1 server-configmap server-cluster-8c64m-datanode2-indexnode4-querynode6-kafka client-configmap client-random-locust-search-60h-1b
master-20220624-23040449 pymilvus 2.1.0dev87
argo test-etcd-no-clean-582t5-1 server-configmap server-cluster-8c64m-datanode2-indexnode4-querynode6 client-configmap client-random-locust-search-60h-1b
pymilvus 2.1.0dev87 2.1.0-20220701-b3a1a60f
query:
kafka
pulsar:
load:
kafka
pulsar:
search:
kafka:
pulsar:
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
looks like search with kafka is 50% slower than it with pulsar, @czs007 could you please take a look?
/assign @czs007 /unassign
doesn't really make sense to me, we didn't rely to much on stream storage in read path right now
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
.
/assign @SimFG pls help on it
@xiaofan-luan: GitHub didn't allow me to assign the following users: it, pls, help, on.
Note that only milvus-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign @SimFG pls help on it
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
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
.