http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12005
--- Comment #2 from Jacek Ablewicz <a...@biblos.pk.edu.pl> --- I did some Q&D measurements trying to estimate what kind of performance penalty we can expect when ditching Zconn caching entirely. While cached Zconn connections are generally not used all that often by Koha, there are some notable exceptions, like (e.g.) authority searches (for each authority record on the result list Koha does one extra search to find out how many biblio records are attached to the specific authority). Creating & immediately destroying Zebra connection - without doing any search with it - is surprisingly lightweight (ca 46 μs per connection). But it goes up to 2.6 - 3.0 ms if the connection was used to perform some actual search. So for a typical case (20 authority search results per request) an extra latency when not caching would be 60 milliseconds or so. Not too bad, considering that: (testing "/cgi-bin/koha/opac-authorities-home.pl?startfrom=0&marclist=any&and_or=and&excluding=&operator=contains&value=&resultsperpage=20&type=opac&op=do_search&authtypecode=PERSO_NAME&orderby=HeadingAsc" page loading time): - mod_perl (semi-persistent; persistent would be ~50 ms faster) with zebra connection caching enabled: 290 ms - mod_perl with zebra connection caching disabled: 350 ms - regular CGI with zebra connection caching enabled: 890 ms -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/
