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

--- Comment #32 from David Gustafsson <[email protected]> ---
(In reply to Fridolin Somers from comment #26)
> Looks great, hight level feature ;)
> 
> In my opinion, one should split between adding the feature of Object Cache
> and using it in item types and libraries.
> Also separate unit tests to be able to see them fail without main patch.
> 
> I understand this uses Koha::Cache::Memory::Lite, is it theoretically
> possible to use Memcached ?

This could be done, but we will be testing this in production as I previously
wrote and most likely weed out any possible remaining issues. Even though the
surface area of caching related bugs is increased by adding this features for
all candidates instead of one by one, it would also be nice to get it all done
in one go and not having to repeat the work for each separate object class. If
the consensus is that it feels safer to perform the change one by one this
could of course be an option.

It's possible to use Nemcached but very little to be gained in terms of
performance while the risk of introducing bugs is substantially increased.
Debugging would also be a nightmare since state could be introduced over a
number of page reloads making reproduction of bugs extremely hard and complex.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to