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 a limb here, but would it also be relevant to (at some distant point in the future) hook this up with the ideas about Koha being able to ”call home” if you allow it in order to keep track of how many installations there are worldwide? I’d like to see larger data sets in order to follow the general trend and it might help in identifying hardware or OS-distros having atypical problems with a specific patch. Regards/Viktor Viktor Sarge Utvecklingsledare Regionbibliotek Halland Kultur i Halland TFN: 035-17 98 73 E-POST: Viktor.Sarge@regionhalland.se<mailto:Viktor.Sarge@regionhalland.se> BESÖKSADRESS: Södra vägen 9, 30180 Halmstad WEBB: www.regionhalland.se/regionbibliotek<http://www.regionhalland.se/regionbibliotek> 18 mar 2014 kl. 11:34 skrev Magnus Enger <magnus@enger.priv.no<mailto:magnus@enger.priv.no>>: 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/