[Bug]: [benchmark] Memory growth during continuous compaction

[elstic]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version:master-20231001-0f14d182
- Deployment mode(standalone or cluster):standalone
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

argo task : fouramf-zqjgb case: test_concurrent_locust_hnsw_compaction_standalone duration: 48 hours

server:

fouramf-zqjgb-69-3149-etcd-0                                      1/1     Running                       0                  2d      10.104.24.221   4am-node29   <none>           <none>
fouramf-zqjgb-69-3149-milvus-standalone-8597c94755-s5trj          1/1     Running                       0                  2d      10.104.12.216   4am-node17   <none>           <none>
fouramf-zqjgb-69-3149-minio-865fcf974c-x4wq2                      1/1     Running                       0                  2d      10.104.12.215   4am-node17   <none>           <none> (cli_client.py:132)

memory usgae:

minio-Data Usage Growth : The minio disk is functioning normally.

Expected Behavior

Memory shouldn't go up.

Steps To Reproduce

1. create a collection  
  2. build an HNSW index on the vector column
  3. insert 100k vectors
  4. flush collection
  5. build index on vector column with the same parameters  
  6. count the total number of rows
  7. load collection
  8. execute concurrent search, query,load, scene_insert_delete_flush 
    (scene_insert_delete_flush steps: 
       1） Insert data  2） Delete the same amount of data 
       4） flush collection ）
  9. step 8 lasts 48h

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @longjiquan /unassign

[stale[bot]]

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[bot]]

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.