Qdrant Vector Database MemMapping Functionality

[semtex1987]

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

yes, currently leveraging qdrant cloud and keep running into out of memory issues since Dify has no ability to enable/disable memmapping for qdrant. This means qdrant instance in qdrant cloud must be sized with memory value that can contain ALL of your vector data

2. Describe the feature you'd like to see

Ability to enable/disable memmapping for qdrant as well as ability to tweak/optimize what data is stored in memory vs what data is stored on disk within qdrant database

3. How will this feature improve your workflow or experience?

Extreme cost savings, scaling vertically or horizontally within qdrant cloud just for RAM is expensive when I have plenty of available disk space in my instance.

4. Additional context or comments

No response

5. Can you help us with this feature?

• [ ] I am interested in contributing to this feature.