milvus: [Bug]: The first insert time of large message(50MB) for new collection is 10x slower than the following insert

Is there an existing issue for this?

I have searched the existing issues

Environment

- Milvus version: master-20211203-1a806a1
- Deployment mode(standalone or cluster): cluster
- SDK version(e.g. pymilvus v2.0.0rc2): 2.0.0rc9.dev22
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

see #12081

first run: end insert, time: 242.40249490737915
second run: end insert, time: 25.066824197769165

Expected Behavior

No response

Steps To Reproduce

No response

Anything else?

No response

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 24 (22 by maintainers)

Most upvoted comments

every insert time of 200 nb for 2000 times Figure_4

XuanYang-cn on Dec 13, 2021

In local terminal: (server and client are not in same machine) In GitHub action: (server and client are in same machine)

zhuwenxing on Dec 14, 2021