zhagnlu

run-cpu-e2e

/run-cpu-e2e

/run-cpu-e2e

run-cpu-e2e

run-cpu-e2e

From log description, it panic when milvus start, connect to etcd failed and retry for many times. maybe env problem, keep watching and check whether reproduce next time

do this test in my local machine, can only load replica = 1 because of memory limit, and from this log, single request cost:  all single request means a...

also do a same test in argo and replica = 3 as upper test case, https://argo-workflows.zilliz.cc/workflows/qa/fouramf-multi-vector-5c6mh?tab=workflow segcore search cost:  it shows almost near 4 seconds proxy lantecy:  it...

compare the low cpu usage case and my normal test: low cpu usage case:  my normal case:  the requery cost has big gap, it means the low cpu...

this issue has two problems, low cpu usage and high latency. actually, it has two different situations considering querynode cpu pressure first one: both low cpu usage for concurrency =...