Summary: | Performance 21.05 - Omnibus | ||
---|---|---|---|
Product: | Koha | Reporter: | Jonathan Druart <jonathan.druart> |
Component: | Architecture, internals, and plumbing | Assignee: | Jonathan Druart <jonathan.druart> |
Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | dcook, martin.renvoize |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7923 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15342 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17819 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 27342, 27343, 30360, 30459, 30460, 30464, 30465, 30467, 30822 | ||
Bug Blocks: | |||
Attachments: |
perfs_20.11_versions
perfs_20.11_cp |
Description
Jonathan Druart
2021-01-05 13:47:38 UTC
Created attachment 114879 [details]
perfs_20.11_versions
Created attachment 114880 [details]
perfs_20.11_cp
I've run some benchmarks using the basic_workflow.t's selenium test, following the same scripts and protocol as https://wiki.koha-community.org/wiki/Benchmark_for_16.11 Script's adjustments (to use KTD instead of KohaDevBox) and results can be found at https://gitlab.com/joubu/koha-misc4dev/-/commits/benchmark_16.11-20.11 The 2 main graphs are attached to this bug report. We clearly see a worrying increase of the time execution between 19.05 and 19.11. I have first focussed on checkin, do some profiling and came to the conclusion that it was caused by ES not updating its index async. A first step has been submitted on bug 27344. Early feedbacks and comments welcomed! (In reply to Jonathan Druart from comment #3) > > Early feedbacks and comments welcomed! I can't speak to Elasticsearch but it would be interesting to see graphs for "add items" and "search". Should this one be closed or renamed? (In reply to David Cook from comment #5) > Should this one be closed or renamed? Closed. |