High Memory consumption on query node #32570
Unanswered
Satyadev592
asked this question in
Q&A and General discussion
Replies: 2 comments 11 replies
-
is there any insertions or deletion on that new collection? |
Beta Was this translation helpful? Give feedback.
10 replies
-
115M 256dim, the original data size is 115GB. Did you set replica_num when you call the load() interface? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Milvus Version: 2.2.9
Number of entries: 115 Million
Dimesnion: 256
Index: HNSW
Query Nodes: 19 nodes with 64GB RAM and 8 cores CPU.
We have been using milvus for over a year in production with minimal issues. We have always seen query node memory increasing over a period of few weeks. We restarted the query nodes to resolve this and were doing this periodically. Recently we added a new collection to the same cluster (although a much smaller collection) ~ 4-5 Million entries (~4% size of the other collection). We are noticing frequent memory spikes as a result of this.
All graphs are for last 1 day:
Query Node Memory Utilisation:
Segment Number by Segment Stage Graph:
Kindly help us debug and resolve this.
Beta Was this translation helpful? Give feedback.
All reactions