[Koha-bugs] [Bug 29623] Cache effective circulation rules
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Tue Jun 14 13:02:28 CEST 2022
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29623
Tomás Cohen Arazi <tomascohen at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tomascohen at gmail.com
--- Comment #36 from Tomás Cohen Arazi <tomascohen at gmail.com> ---
(In reply to David Cook from comment #12)
> (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*?
MySQL will be doing disk I/O on the first request for the same thing. I'm
pretty sure the caching strategy in MySQL is far better than ours and
memcached.
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list