Milvus can cause the CPU to suddenly soar to 90%

[a8734550]

My host only runs milvus and the CPU is Intel ultra9; The answer I found online is that it is caused by timed index writing. How can I modify the configuration item to prevent CPU from being fully occupied? Sometimes it can also cause my Docker container to crash and exit

[a8734550]

My Milvus version 2.5.2 has a host memory of 192GB and currently has 4 collections with approximately 6500W of data;

[yhmo]

Is your Milvus standalone?
For standalone, all nodes(coordinators, querynode, datanode, indxnode) are running in the same process, they share the same CPU resource and memory resource.

[a8734550]

Thank you for your reply. I am using milvus standalone, so is this a normal occurrence? Is there any configuration to reduce CPU usage, even if it can be processed slower

[yhmo]

Yes, for standalone, it is a normal behavior. Once indexnode starts an index task, it will try using all CPU cores to build index.

[xiaofan-luan]

It's highly recommend to seperate index node and queyrnode in production env, especially large use case.

In Milvus 2.5.4 we do have a improvement on cpu usage for standalone. Ideally you should see the cpu usage to be round 75%