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

The plugin reads large files very slowly. It turns out that the fixed number of characters to read is 512 in the code. #12042

New Issue
Closed
opened 2026-02-21 19:05:26 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:05:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @yj11 on GitHub (Mar 24, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v1.1.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Since the number of bytes read from the image is too small and the value is fixed in the code, the performance is very low and the time consumption is too long when reading large images. We hope to turn this number into a configuration item for easy modification.

Image

✔️ Expected Behavior

Please put 512 in the configuration file

❌ Actual Behavior

Slow file reading performance.

Originally created by @yj11 on GitHub (Mar 24, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version v1.1.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Since the number of bytes read from the image is too small and the value is fixed in the code, the performance is very low and the time consumption is too long when reading large images. We hope to turn this number into a configuration item for easy modification. ![Image](https://github.com/user-attachments/assets/e8c37187-9be3-4ea8-bf6b-e3a88763610a) ### ✔️ Expected Behavior Please put 512 in the configuration file ### ❌ Actual Behavior Slow file reading performance.
yindo added the 💪 enhancement label 2026-02-21 19:05:26 -05:00
yindo closed this issue 2026-02-21 19:05:26 -05:00
yindo commented 2026-02-21 19:05:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 24, 2025):

Hi, @yj11. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Performance bottleneck reported in the plugin when reading large files.
  • Fixed character read limit of 512 affects handling large images.
  • Issue pertains to version v1.1.0 of the self-hosted Docker setup.
  • Suggestion to make the character read limit configurable.
  • No comments or further developments on the issue yet.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Apr 24, 2025): Hi, @yj11. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - Performance bottleneck reported in the plugin when reading large files. - Fixed character read limit of 512 affects handling large images. - Issue pertains to version v1.1.0 of the self-hosted Docker setup. - Suggestion to make the character read limit configurable. - No comments or further developments on the issue yet. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 💪 enhancement
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#12042
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?