I'm not a developer, but I lurk on this list anyway. I manage a very large Koha consortia in Kansas that has faced significant speed issues over the last year with our system, as some of you may be aware. 

I welcome any and all avenues of trying to pinpoint potential speed bottlenecks in the code! Targeting checkout and checkin processes and code, especially, for this implementation would be fantastic. 

Thanks for pursuing this.

Heather Braum
NExpress Coordinator
Resource Sharing Librarian
Northeast Kansas Library System
hbraum@nekls.org

"The illiterate of the 21st century will not be those cannot read and write, but those who cannot learn, unlearn, and relearn." ~Alvin Toffler, *Rethinking the Future*





On Tue, Mar 18, 2014 at 5:34 AM, Magnus Enger <magnus@enger.priv.no> wrote:
Dear Community,

I spent the last day of the hackfest in Marseille hacking together a
"proof of concept" script for checking changes in the performance of
Koha over time:

https://github.com/digibib/kohaprofile

The idea is to step x commits back in time, run a bunch of timed
tests/benchmarks on Koha, take one step forwards in time, run the
tests again etc. Hopefully this might be able to show us what the
general trends are, and if there are any changes that lead to
noticeable increases in response times.

If you run the same benchmark a few times in a row, the response times
vary quite a bit. Perhaps there is too much "noise" for this to be
really useful. (To mitigate this, the script can run the tests y
number of times and record the average time. Perhaps there are better
ways to deal with the statistics of this, like removing the fastest
and the slowest time etc.)

This is a "proof of concept", so I would be really interested in
hearing your thoughts on it. If the concensus is that it does not
yield interesting data, I'll abandon the project. If people think it
has some merit I would be more than happy to accept pull requests for
improving it. :-)

See the README for some ideas for improvements.

Does anyone know if there are tools that can do what I'm trying to
accomplish here (specifically the idea of stepping through Git history
to check performance) already?

Best regards,
Magnus
_______________________________________________
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/