Fellow Kohackers, Do any of you have a favour script or suite of scripts (or even a method) for doing load testing against a Koha installation? I know there are some scripts available in misc/load_testing, but my understanding is they aren't terribly useful or current. Is that correct? Something that can throw a user-configured amount of punishment at a Koha server, then report on the results, would be ideal. The output should include both the user perspective (response times) and what's happening on the machine (memory/CPU usage, query times, etc) in the context of the machine's specifications. If all this data can be compiled for various configurations, I think we'd have the makings of a fine, evidence-based Koha Tuning Guide. Thanks, all! -Ian -- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth 732 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
Le 14/04/2011 17:10, Ian Walls a écrit :
Fellow Kohackers, Hi
Do any of you have a favour script or suite of scripts (or even a method) for doing load testing against a Koha installation? I know there are some scripts available in misc/load_testing, but my understanding is they aren't terribly useful or current. Is that correct?
quite. I did use ab and siege. But siege is my favourite. The nice thing with siege is that you can 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 Lifting the server siege.. done. Transactions: 450 hits Availability: 100.0 % Elapsed time: 64.00 secs Data transferred: 2.82 MB Response time: 4.25 secs Transaction rate: 7.03 trans/sec Throughput: 0.04 MB/sec Concurrency: 29.92 Successful transactions: 31806 Failed transactions: 0 Longest transaction: 7.37 Shortest transaction: 0.00 The nice thing is that you can use -v to see which elements have errors.
Something that can throw a user-configured amount of punishment at a Koha server, then report on the results, would be ideal. The output should include both the user perspective (response times) and what's happening on the machine (memory/CPU usage, query times, etc) in the context of the machine's specifications.
Having both in one software would not be possible unless you have a client and server script to do that... But then ... it could be like an auditer having some interests in the place. But I may be mislead. You can use munin or nagios to inspect the server while load testing.
If all this data can be compiled for various configurations, I think we'd have the makings of a fine, evidence-based Koha Tuning Guide.
We already have bits in the koha-devel list for that. We would need to compile those bits into an administration/setup guide though on the wiki. #idea Hope that helps. -- Henri-Damien LAURENT BibLibre
I created the wiki page... go for it! (great idea, by the way) http://wiki.koha-community.org/wiki/Koha_Tuning_Guide Liz On Apr 14, 2011, at 10:23 AM, LAURENT Henri-Damien wrote:
Le 14/04/2011 17:10, Ian Walls a écrit :
Fellow Kohackers, Hi
Do any of you have a favour script or suite of scripts (or even a method) for doing load testing against a Koha installation? I know there are some scripts available in misc/load_testing, but my understanding is they aren't terribly useful or current. Is that correct?
quite. I did use ab and siege. But siege is my favourite. The nice thing with siege is that you can 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 Lifting the server siege.. done. Transactions: 450 hits Availability: 100.0 % Elapsed time: 64.00 secs Data transferred: 2.82 MB Response time: 4.25 secs Transaction rate: 7.03 trans/sec Throughput: 0.04 MB/sec Concurrency: 29.92 Successful transactions: 31806 Failed transactions: 0 Longest transaction: 7.37 Shortest transaction: 0.00
The nice thing is that you can use -v to see which elements have errors.
Something that can throw a user-configured amount of punishment at a Koha server, then report on the results, would be ideal. The output should include both the user perspective (response times) and what's happening on the machine (memory/CPU usage, query times, etc) in the context of the machine's specifications.
Having both in one software would not be possible unless you have a client and server script to do that... But then ... it could be like an auditer having some interests in the place. But I may be mislead.
You can use munin or nagios to inspect the server while load testing.
If all this data can be compiled for various configurations, I think we'd have the makings of a fine, evidence-based Koha Tuning Guide.
We already have bits in the koha-devel list for that. We would need to compile those bits into an administration/setup guide though on the wiki. #idea Hope that helps. -- Henri-Damien LAURENT BibLibre _______________________________________________ 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/
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
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
2011/4/15 Ian Walls <ian.walls@bywatersolutions.com>:
I very much look forward to trying out siege, and seeing what data can be gathered both client side and server side.
Here at UNC we have used 'ab' and 'jmeter' for concurrent load testing. We used tcpdump on each host and some perl scripts I wrote to process tcpdum's output (so we can have a measure of completed connections, completed connections average time, etc). Saludos To+
participants (5)
-
Ian Walls -
LAURENT Henri-Damien -
Liz Rea -
Paul -
Tomas Cohen Arazi