Bug 24778 - Move from Memcached to Redis to solve L1 caching issues?
Summary: Move from Memcached to Redis to solve L1 caching issues?
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-02 17:46 UTC by Kyle M Hall (khall)
Modified: 2024-01-09 23:28 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall (khall) 2020-03-02 17:46:54 UTC 
Would it be worthwhile to switch from Memcache to Redis? Redis has pub/sub which in theory would allow all processes to listen for syspref changes and update their L1 caches if necessary.

What made me think of this is bug 23640

I have no idea if this is worth the time and effort, but it seems like it would solve the major issue we have with memcached.
Comment 1 Katrin Fischer 2024-01-06 13:52:08 UTC 
This was filed almost 4 years ago - have we come to a decision about this?
Comment 2 Kyle M Hall (khall) 2024-01-09 14:53:30 UTC 
(In reply to Katrin Fischer from comment #1)
> This was filed almost 4 years ago - have we come to a decision about this?

I don't think it's ever been discussed anywhere other than me filing this bug.
Comment 3 David Cook 2024-01-09 23:28:17 UTC 
I don't think it would really work anyway. We need to flush the L1 caches after each request for more reasons than just sysprefs as well I believe.