https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15851
--- Comment #53 from David Cook <[email protected]> --- yaz-client: e 37500 hits .09 seconds Koha: e 37500 hits 2.110 seconds (2 seconds being loading Perl modules, so .110 sec) yaz-client: the 1125000 hits 3.39 seconds Koha: the 1125000 hits 5.315 seconds (2 seconds being loading Perl modules, so 3.315 sec) If we convert from async code to sync code, we can get the following: 1125000 hits 3.78 seconds (2 seconds being loading Perl modules, so 1.78 sec) If we comment out the code after the search(), we can see that it still takes 3.7-4 seconds to run, so the time delay appears to be on the Zebra side. I see high CPU usage but not high memory usage, so it looks like it's processing something. Of course, Zebra is a bit of a black box for us. For a Plack enabled Koha, my guess is that this search should have a minimal impact, unless a bib record has hundreds of thousands/millions of articles referencing it. The highest hit is probably going to be < 100, and since the time is dependent on the size of the search result rather than the size of the index, database size should be irrelevant. The biggest impact in terms of performance will probably be loading Perl modules via "use Koha::SearchEngine::Search". For Plack, this will be a once off for a worker that hasn't loaded opac-detail.pl before. For CGI, it could add 1-2 seconds of latency each time opac-detail.pl is loaded. -- 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/
