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

[PR #19493] feat: enable Redis client-side caching #29159

New Issue
Closed
opened 2026-02-21 20:44:59 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:44:59 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/19493

State: closed
Merged: Yes

Summary

Background:

Action:

  • Enable RESP3 support in Redis connections
  • Set Client-side caching in Redis connection configs, as default , 10000 items cached with LRU for default eviction policy on client side in OrderedDict of Python
  • Bump redis-py from 5.0.x to 6.0.x to satisfying >5.1.0 requirement and it also brings support for latest Redis 8

Screenshots

Before After
... ...

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/19493 **State:** closed **Merged:** Yes --- # Summary - to close #19494 Background: - Client-side caching is an important feature introduced since Redis 6.x in 2020, greatly reducing network usage while ensuring consistency. - It relies on [RESP 3 protocol](https://github.com/redis/redis-specifications/blob/master/protocol/RESP3.md), which is supported since Redis 5. - Redis-py supports Client-side caching since v5.1.0 in Nov 2024, https://github.com/redis/redis-py/releases/tag/v5.1.0 - Consistency in client-caching is guaranteed as once the tracked key is invalidated on server side all the subscribed clients get noticed. See the manchanism in Redis docs: https://redis.io/docs/latest/develop/clients/client-side-caching/ Action: - Enable RESP3 support in Redis connections - Set Client-side caching in Redis connection configs, as default , 10000 items cached with LRU for default eviction policy on client side in OrderedDict of Python - Bump `redis-py` from 5.0.x to 6.0.x to satisfying >5.1.0 requirement and it also brings support for latest Redis 8 # Screenshots | Before | After | |--------|-------| | ... | ... | # Checklist > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:44:59 -05:00
yindo closed this issue 2026-02-21 20:44:59 -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 pull-request
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#29159
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?