https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17189
--- Comment #5 from Jacek Ablewicz <[email protected]> --- (In reply to Jacek Ablewicz from comment #4) > Hmm, IMO most serious limitation of this approach/implementation is that > having separate cache object instances for 1) sysprefs 2) config and 3) > everything else will result in opening 3 different connections to (the very > same) memcached daemon per script/plack worker. Under plack, the 2nd > connection will be used just once. OTOH - those 3 connections to memcached server do not seem to have any significant practical consequences, I did some tests and it's only 150-200 microseconds per connection. In fact it's probably a bit faster then unpatched version (there are 2 separate connections being made in unpatched master) if the Cache::Memcache loading time is taken into account. Memcached is event driven (so the added memory footprint on it's side is negligible, forking not involved) and it is taking the increased burden surprisingly (extremely!) well. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
