[Bug]: no memory protection for proxy

[congqixia]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

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

Current Behavior

when client search/query milvus with large concurrency and output has large vector of big dimension, proxy may crash with OOM

Expected Behavior

there shall be a memory protection for proxy component

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @congqixia /unassign

[xiaofan-luan]

is it because of large topk + nq + output field?

What kind of limitation will we set?

[congqixia]

is it because of large topk + nq + output field?

What kind of limitation will we set?

yes. when we test proxy performance with "infinite" querynode, when collection schema has large vector field, say 16384, and output fields contains vector field, proxy crashed due to OOM.

[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.