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
This sounds like a good idea - nice work! I don’t feel that I am capable of
really assessing all pros and cons for developers, but I’d still like to say
this: speed is essential and everything that helps to ensure that feature creep
doesn’t slow Koha down over time is welcome.
I’m going out on
Le 18/03/2014 11:34, Magnus Enger a écrit :
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
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!
On Tue, Mar 18, 2014 at 11:07 AM, Paul Poulain
paul.poul...@biblibre.com wrote:
Le 18/03/2014 11:34, Magnus Enger a écrit :
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
