langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 04:25:29 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Qdrant Vector Database MemMapping Functionality #2803

New Issue
Closed
opened 2026-02-21 17:50:12 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:50:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @semtex1987 on GitHub (Apr 29, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • 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.
Originally created by @semtex1987 on GitHub (Apr 29, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [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.
yindo added the 👻 feat:rag label 2026-02-21 17:50:12 -05:00
yindo closed this issue 2026-02-21 17:50:12 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 👻 feat:rag
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#2803
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?