During peak business hours, such as high-volume data writes during the day, a Milvus cluster may experience high CPU and memory usage on its Data Nodes and Index Nodes. This can lead to slow index building, compaction delays, or even node restarts due to out of memory (OOM) errors. Conversely, during off-peak hours or at night, these nodes have low resource utilization, resulting in wasted computing resources.