[Koha-bugs] [Bug 29623] Cache circulation rules

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue May 31 02:46:54 CEST 2022


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29623

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #12 from David Cook <dcook at prosentient.com.au> ---
(In reply to Martin Renvoize from comment #9)
> Silly question... why do this just at the request caching level?
> 
> I had a bit of a deep dive into our caching strategies yesterday to get
> myself back up to speed...
> 
> Is it slower to fetch a key from Memcached once (to populate the L1 per
> request) than it is to fetch it from MySQL (to populate the same L1 per
> request)?.. or am I totally misunderstanding our caching code?

The TCP speed is probably comparable although the MySQL is going to be doing
some disk I/O while Memcached is all in memory so in theory Memcached should be
faster, but the difference might be imperceptible with a low load and good
disk*? 


*I have a different app that does a lot of I/O on very bad disks and even doing
simple lookups can be hard when the disks are busy with other tasks

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list