[Koha-devel] Benchmarks - prior to the 3.22 release

[Mirko Tietgen]

I set up Koha 3.22 on a Raspberry Pi 2, thinking about releasing an
image so people can play with it. I was hoping to get results in the
way I got back when I did it with the very first Raspi, which was
slow, but kind of usable with Plack.

With Plack enabled I get pretty much the search times I had with the
Raspberry Pi 1 (the single cpu, 256mb RAM one) without Plack,
running Koha 3.8. (zebra facets disabled)

I have not tried the old benchmark script (or tried Jonathan's test)
yet, but so far I share Jonathan's findings.

That is in no way meant to bad-mouth a great new release, but the
question probably is, do we just accept it that way or can we do
something about it? And what could that be?

Or is it the cost that comes with having a lot of great new features
and internal changes? Hardware is getting faster too, so maybe
comparing a 2015/16 release to one from 1,5 years (3.16) or even 3,5
years (3.8) ago does not make sense?

Cheers,

Mirko



Jonathan Druart schrieb am 10.11.2015
> I use plack with the koha.psgi file from the source
> (misc/plack/koha.psgi) and the Proxy/ProxyPass directives in the
> apache config.
> 
> For more info on what does the tests, please see the first lines on
> the wiki page, which point to bug 13690 comment 2:
> ===
> I have created a selenium script (see bug 13691) which:
> - goes on the mainpage and processes a log in (main)
> - creates a patron category (add patron category)
> - creates a patron (add patron)
> - adds 3 items (add items)
> - checks the 3 items out to the patron (checkout)
> - checks the 3 items in (checkin)
> ===
> 
> 
> 2015-11-09 20:19 GMT+00:00 Tomas Cohen Arazi <tomascohen at gmail.com>:
>>
>>
>> 2015-11-09 13:30 GMT-03:00 Jonathan Druart
>> <jonathan.druart at bugs.koha-community.org>:
>>>
>>> Hi devs,
>>>
>>> Please have a look at the these benchmarks:
>>>
>>> http://wiki.koha-community.org/wiki/Benchmark_for_3.22
>>
>>
>> It is expected that broader DBIC usage would have more footprint [1]. I
>> wonder what your Plack setup is, as the packages integration uses Starman
>> with prefork, so the load time should not be user-noticeable.
>>
>> Hum...
>>
>> I agree with Paul A, that running in Plack feels so close to zero-time, that
>> those numbers sound unrealistic. Maybe we should go back to caching sysprefs
>> (you could test that if you have the VM ready for it) and have the workers
>> last shorter time (something between 1 and 5 requests) [2].
>>
>> [1] Only as an example, we are now retireving sysprefs through DBIC.
>> [2] Dobrica mentioned this in Marseille. I don't recall how many beers we
>> had before that.
>>
>> --
>> Tomás Cohen Arazi
>> Theke Solutions (http://theke.io)
>> ✆ +54 9351 3513384
>> GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at 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/
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20151127/89512040/attachment.pgp>