-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Bug]: [benchmark][standalone] Each request RT gradually increases in concurrent DDL scene #32277
Comments
it looks obviously that the scene_hybrid_search_test is getting more and more slow. /unassign |
CreateCollection and DropCollection include scene_test and scene_hybrid_search_test I have initially checked with @czs007 . It is caused by too many collection metrics contained in rootCoord. |
might be due to our snapshot gc issue. all the meta takes 24 hours to garbage collected |
@wangting0128 any updates for milvus 2.4 latest build? I believe rootcoord might not be the bottleneck any more with 10K+ collections. |
There is no update. I will test again using the latest master branch image today |
Verified with image: master-20240520-555df49d-amd64, the problem of request RT rising seems to have been alleviated. |
The 2.4 branch seems to still have this problem argo task:fouramf-pxv6r-release server:
client pod name: fouramf-pxv6r-release-3102168818 test result:
|
some of the data might leaked in coordinator, causing the latency goes up. @shaoting-huang |
Is there an existing issue for this?
Environment
Current Behavior
argo task: fouramf-multi-vector-d5bqx
test case name: test_concurrent_locust_50m_multi_ivf_sq8_ddl_dql_standalone
server:
CreateCollection
DropCollection
DescribeCollection
DescribeIndex
GetCollectionStatistics
Flush
LoadCollection
GetLoadState
client pod name: fouramf-multi-vector-d5bqx-3501960532
client monitor:
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
test result:
The text was updated successfully, but these errors were encountered: