July 2012 - Koha-devel - lists.koha-community.org

Re: [Koha-devel] "The Plack effect" benchmarked
by Paul Poulain 11 Jul '12

11 Jul '12

Le 06/06/2012 13:36, Mark Tompsett a écrit : > Greetings, Hi Mark, (answer to koha-devel, as it's of general interest) > These results look good, but how much memory is on the machine you are > testing this on? Would it have the same effect in a VM server type > environment limited to 204MB? Is there an amount of memory which makes > it behave at similar or worse speeds? I think you missed a 8, and speak of 2048 and not 204MB :D I haven't tested/checked memory, but what I know for sure is that it costs only a small amount of memory. Plack pre-load a lot of things that are loaded on every page by cgi-bin anyway. So you would have 'spent' that memory at run time. Depending on Apache configuration, if 5 ppl are requesting a page at the same time, 5 cgi-bin are launched and 5x memory is consummed. So if you run starman instead of plackup (starman being multi-thread, plackup single thread), the result will be the same. What we have to be *very* careful with is memory hole that result in an always increasing memory consumption. In CGI mode, as everything is freed/deleted after each page, any memory hole is painless. With plack, memory hole will pile up and, at the end ... booom ! (All of this being not measured, so unguaranteed) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

4 4

"The Plack effect" benchmarked
by Paul Poulain 11 Jul '12

11 Jul '12

Hi, Just in case some of you have doubts about the interest of having Plack for staff interface, here is a result of misc/load_testing/benchmark_staff.pl made with and without Plack: benchmarking WITH Plack: Step 1: staff client main page 4178ms 4.786 pages/sec Step 2: catalog detail page 9991ms 2.001 biblios/sec Step 3: catalogue search 5631ms 3.551 biblios/sec Step 5: patron detail page 7037ms 2.842 borrowers/sec Step 5: patron search page 11800ms 3.389 borrowers/sec Step 6a circulation (checkouts) 8967ms 2.23 checkouts/sec Step 6b circulation (checkins) 13880ms 1.44 checkins/sec all transactions at once 55433ms 3.247 operations/sec (note = tests run with plackup, not with starman, the all transaction at once results would probably be better with starman) benchmarking WITHOUT Plack: Step 1: staff client main page 28576ms 0.699 pages/sec Step 2: catalog detail page 39106ms 0.511 biblios/sec Step 3: catalogue search 55524ms 0.36 biblios/sec Step 5: patron detail page 34610ms 0.577 borrowers/sec Step 5: patron search page 64964ms 0.615 borrowers/sec Step 6a circulation (checkouts) 37907ms 0.527 checkouts/sec Step 6b circulation (checkins) 39129ms 0.511 checkins/sec all transactions at once 138298ms 1.301 operations/sec It appears that the speed improvement is more x3 or x4 than x1.5 as I usually say -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 1

Request for moremember page...
by Paul Poulain 10 Jul '12

10 Jul '12

Hello Koha-devel, The moremember.pl page, that display a patron detail, contain a lot of informations : patron detailled information (including some that are not daily useful), Patron image management (if activated), patron extended attributes (if used), patron messaging preferences (if used), checkout fines, holds I just pushed a new feature, that let the library upload any file attached to the patron (bug 8130) Overall, if someone want to relook this page, I think many ppl would applaude ! My suggestion (but I'm not a designer) : add tabs. The first tab displaying basic information & checkout/fines/holds, other displaying other less important informations. Note : on my 22" screen, the checkouts/fines/hold does not appear on the visible part of the screen, it's a shame, that's a major information. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

5 5

Kohacon 2013 voting: one week left
by Mirko 09 Jul '12

09 Jul '12

Hello everybody, just a little reminder that there is one week left to vote for the Kohacon 2013 location. If you have not done it so far, do it now! See the proposals here: http://wiki.koha-community.org/wiki/Kohacon2013 Vote here: http://survey.web2learning.net/limesurvey/index.php?sid=91534&lang=en - Mirko

1 0

Blog post about BibLibre development rebases
by Claire Hernandez 09 Jul '12

09 Jul '12

Hello all, I wrote a blog post about our developments and the community integration. You can read it here: http://drupal.biblibre.com/en/blog/entry/biblibre-developpments-rebase-and-… It is about: - 2012 goals development rebases - Vision and roadmap - Progress and learnt of january and february - Why the community needs you The purpose was to make visible our work and explain how people can invest into this development integration (for example for our french customers). If you have questions, juste ask. Have a good day, Claire;

5 9

Signing-off a patch for a customer
by Paul Poulain 06 Jul '12

06 Jul '12

Hello koha-devel, I just pushed a follow-up for bug 6858. If you look at the patch, you'll see that the author is from BibLibre, as well as the sign-offer. But if you look more carefully on the patch comments, you may understand that Stephane Delaye has signed-off "in the name of the library". We're facing here a case where the library don't want/can't sign-off their patch (they don't know how to do it and don't want to bother with doing it. They just said this patch worked for them) At BibLibre, we have 3 project managers: Stéphane Delaye / Gaetan Boisson / François Charbonnier. They are librarians and are doing the glue between the library our customer and our developers. they know how to sign-off a patch. I want, in this mail, request that those 3 ppl from BibLibre (and only them) can be sign-offers for patches written by another BibLibre developer, once the library has confirmed it works. I propose that we define a standard message, something like Signed-off-by: Delaye Stephane <stephane.delaye(a)biblibre.com> patch validated by <LIBRARY NAME>, signed-off in their name Can I have your agreement with this idea ? (of course, in case another support provider has the same kind of situation, this would also be applicable. It's not something I want for BibLibre only) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

13 33

KohaCon 13 Survey Problem
by Nicole Engard 06 Jul '12

06 Jul '12

Hello all, I wasn't clear when I sent out the survey for KohaCon and per a discussion in #koha I'm coming to you to see if you'd like me to rerun the survey so you can update your votes. Here's how it works - and how it worked in previous years: If you vote for someplace as #1 it gets 5 points, #2 it gets 4 points, and so on. In the end we tally the points to see where the conference takes place. That way if everyone picks one place as #1 but more people pick it as second and third it still might win. So basically if you won't go somewhere no matter what then don't vote for that location and it will get no points from you. This means that those of you who didn't know the rules - because I didn't make it clear at all (my fault) might not have voted the way you would have if you knew the rules. So my question to you all is ... should I close voting and put out a new call for votes explaining the procedure more clearly - or do we just carry on as we are? Nicole

11 17

Re: [Koha-devel] Bugzilla Statistics
by Marcel de Rooy 06 Jul '12

06 Jul '12

> To that end, I have been creating the statistics of signoffs > http://blog.bigballofwax.co.nz/2012/07/01/bugzilla-statistics-for-june-2012/ Interesting statistics. I was trying to get these results from Bugzilla too. So I tried this search: Changed: (is greater than or equal to) 2012-06-01 Status: (changed to) Signed off Status: (changed after) 2012-06-01 *** This after seems to be an inclusive one Status: (changed before) 2012-06-30 23:59:59 Note that I got 214 results. More than the 194 that Chris counted. It appears however that Bugzilla is not completely reliable here. By example: It includes report 7848. History shows that Status changed to Signed-off on May 31 and again on July 2. The status change in June was to Failed QA. So it should not have been included? Any idea why? Another thought: A report that was signed off twice in June, cannot be counted twice via Bugzilla search.

2 1

Koha Release Manager monthly newsletter 8 published
by Paul Poulain 04 Jul '12

04 Jul '12

Hello Koha users & developers, I just published my monthly RM newsletter at http://koha-community.org/koha-release-manager-newsletter-8-2012-06/ Enjoy -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

About IRC meeting & voting
by Paul Poulain 04 Jul '12

04 Jul '12

Hello world, Sorry for missing yesterday IRC meeting, but after 10 days away from home, my family needed me (and it was 8PM here !) During the meeting, Owen said, as a joke: oleonard> 24-hour meeting, votes ever hour, day-end averages win. but i'm not sure it should be a joke: there is always someone sleeping or (wanting to) during the IRC meeting. So shouldn't we vote not during IRC meeting, but just confirm the vote, that is made during a period before the IRC meeting, on an other tool, like wiki, gdoc, yell +1 / 0 / -1 on the mailing list, a tool like http://www.ballotbin.com/ (untested, just found it in google) or whatever you want. I think that would also help more people being involved: attending an IRC meeting is, for some, a too high barrier (in France, there's a barrier with the language, for example). More vote, more involvement,... sounds a good deal isn't it ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

8 11