Paul, I've also found search to take 4 seconds most times (sometimes higher, if the system is under some kind of load). Two recent patches have been submitted to reduce this to 2 seconds (by disabling Authorized Value images and search results COinS, which both took up a lot of processing time; these features can now be toggled with system preferences). HDL, I very much look forward to trying out siege, and seeing what data can be gathered both client side and server side. Thanks all! -Ian On Thu, Apr 14, 2011 at 7:00 PM, Paul <paul.a@aandc.org> wrote:
At 05:23 PM 4/14/2011 +0200, LAURENT Henri-Damien wrote: [snip]
an input a url file that will do
the search with all the url provided. I used a TransferLog from apache, (One or two days) edited to suit the siege format for input and that was VERY useful for load testing.
http://opac.distant/cgi-bin/koha/opac-search.pl?idx=&q=l%27explosion+de+la+communication provides that kind of output
** SIEGE 2.70 ** Preparing 30 concurrent users for battle. The server is now under siege...^C
[snip]
Response time: 4.25 secs
[snip]
Longest transaction: 7.37
Shortest transaction: 0.00
Interesting... we have also been doing some timing (imho, one of Koha's weaknesses) and had empirically come up with 4-7 seconds. Please see my notes para 2. a) at <http://aandc.org/koha/>. (This page also contains other questions - if anyone has the time and patience to assist.)
Best regards,
Paul Tired old sys-admin _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth 732 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal