verify performance of RMB26 versions of mod-inv-s, mod-circ-s and mod-users

Description

Please check if there are any performance regressions or API errors on folio-perf-platform when running with mod-circulation-storage, mod-inventory-storage and mod-users based on RMB 26. Please report here any particular regressions as compared to previous succesfull runs.

Also, please review RMB logfiles for those modules to check for any WARN messages about missing indexes, e.g missing FT, GIN and BTREE indexes for specific queries. Please report the occurrences of those warnings and corresponding CQL and SQL queries here.

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Hongwei Ji July 18, 2019 at 8:28 PM

Latest perf result looks good. https://github.com/folio-org/mod-inventory-storage/blob/master/ramls/instance.json. The only really slow ones are searching instances by joining other tables.

Julian Ladisch July 16, 2019 at 11:40 AM

The warning is from CQL2PG, the "CQL >>> SQL" message is from RMB CQLWrapper.
Therefore moving the warning below the CQLWrapper line is not possible.

Hongwei Ji July 15, 2019 at 6:28 PM

The fix made by (match FT index with FT search in RMB 26.2.0) made a big difference. The new array syntax search time is down from a few minutes to under 100ms. As of now, there are three slow tests left.
1) search item by item barcode. This is due to a mismatch between index and query. Should be an easy fix. I will resolve this today.
2 and 3): checkin and checkout. We have to wait a) the latest mod-circulation-storage build (with RMB 26.2.0). Hopefully the PR this morning to bump up ui-users dependency to loan-storage interface will resolve this); b) audit_table PK violation issue get resolved (WIP by ).

BTW , RMB does log the CQL query and SQL right after the WARNINGS message. For example:

Jakub Skoczen July 15, 2019 at 9:07 AM

It would be great if those WARNINGS above logged also the CQL query (or at least index relation term for this particular node of the query)

Jakub Skoczen July 15, 2019 at 9:05 AM

How is the performance after those updates? Did it help if any of the cases? What slow queries remain?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Core: Platform

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 3, 2019 at 2:10 PM
Updated June 3, 2020 at 4:39 PM
Resolved July 18, 2019 at 8:29 PM
TestRail: Cases
TestRail: Runs