...

This is a report for a series of Check-in-check-out test runs against the Honeysuckle release.

Jira Legacy

server	System JiraJIRA
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	PERF-135

...

Check-out: Honeysuckle is slower by 9%-28% than Goldenrod
Check-in: 4%-22% slower than Goldenrod
APIs turned slower in Honeysuckle: GET /automated-patron-blocks/{id} (150% slower) and GET /circulation/loans (60%). These are covered by MODPATBLK-70 and CIRC-1014, respectively
Okapi v4.3.3 seem to be using 2x-3x CPU cycles than in v1.3.2 (Goldenrod). Potential issue found with the logging methods OKAPI-964
mod-pubsub has a memory leak that would drag down performance under high loads (see section on longevity test): MODPUBSUB-136
Caching Okapi tokens in Okapi reduced mod-authtoken's CPU usage by over 90%
Database's memory usage improved dramatically from Goldenrod's - little memory consumptions observed.

...

Subsequent investigations (
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key PERF-140
AND
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CIRC-1014
) on GET /circulation/loans do not show degradations by the API itself. We hypothesize that other API calls that were executed during the test run may have dragged down the response time, particularly if it was trying to read and write to the same rows in the database at the same time.

...

Honeysuckle tests revealed the following missing indexes:

mod-circulation-storage missing indexes

Code Block

WARNING: Doing LIKE search without index for jsonb->>'requestId', CQL >>> SQL: requestId == 920e1d64-c221-48a0-a44d-ff50f3ad6cd6 >>> lower(f_unaccent(jsonb->>'requestId')) LIKE lower(f_unaccent('920e1d64-c221-48a0-a44d-ff50f3ad6cd6'))
WARNING: Doing FT search without index for request.jsonb->>'requesterId', CQL >>> SQL: requesterId = ae4c1cf3-0738-4465-8112-e75089e5b5c6 >>> get_tsvector(f_unaccent(request.jsonb->>'requesterId')) @@ tsquery_phrase(f_unaccent('ae4c1cf3-0738-4465-8112-e75089e5b5c6'))
WARNING: Doing FT search without index for request.jsonb->>'pickupServicePointId', CQL >>> SQL: pickupServicePointId = 7068e104-aa14-4f30-a8bf-71f71cc15e07 >>> get_tsvector(f_unaccent(request.jsonb->>'pickupServicePointId')) @@ tsquery_phrase(f_unaccent('7068e104-aa14-4f30-a8bf-71f71cc15e07'))
WARNING: Doing LIKE search without index for patron_action_session.jsonb->>'patronId', CQL >>> SQL: patronId == d7cabcb2-7431-43ea-a2cc-0dfe5bee17c6 >>> lower(f_unaccent(patron_action_session.jsonb->>'patronId')) LIKE lower(f_unaccent('d7cabcb2-7431-43ea-a2cc-0dfe5bee17c6'))
WARNING: Doing LIKE search without index for patron_action_session.jsonb->>'actionType', CQL >>> SQL: actionType == Check-out >>> lower(f_unaccent(patron_action_session.jsonb->>'actionType')) LIKE lower(f_unaccent('Check-out'))

...

Code Block

WARNING: Doing LIKE search without index for accounts.jsonb->>'userId', CQL >>> SQL: userId == e96618a9-04ee-4fea-aa60-306a8f4dd89b >>> lower(f_unaccent(accounts.jsonb->>'userId')) LIKE lower(f_unaccent('e96618a9-04ee-4fea-aa60-306a8f4dd89b'))
WARNING: Doing LIKE search without index for accounts.jsonb->'status'>>'name', CQL >>> SQL: status.name <> Closed >>> lower(f_unaccent(accounts.jsonb>'status'->>'name')) NOT LIKE lower(f_unaccent('Closed'))
WARNING: Doing LIKE search without index for manualblocks.jsonb->>'userId', CQL >>> SQL: userId == a79b533d-8f29-4be1-9415-5f5cd936623b >>> lower(f_unaccent(manualblocks.jsonb->>'userId')) LIKE lower(f_unaccent('a79b533d-8f29-4be1-9415-5f5cd936623b'))

Results for okapi-4.5.2

Response Times

...

Results for okapi-4.5.2 for 1,5,8,20 users for 30 minute run. From the response times below, the average Check-out for 20 users is slower. On average 60% slower than okapi-4.3.3.

'+' means performance improvement from okapi-4.3.3

'-' means performance degradation from okapi-4.3.3

For 20 users - 4 requests failed out of 113642

Response Times

	Average (seconds)		50th %tile (seconds)		75th %tile (seconds)		95th %tile (seconds)
	Check-in	Check-out	Check-in	Check-out	Check-in	Check-out	Check-in	Check-out
1 user	0.971	2.072	0.92	1.906	1.013	2.093	1.326	2.905
5 users	1.

003

092 +

2.584 -

0.978 +

2.

1140.9251.9471.0552.2351.4583.1498 users1.2172.4671.0992.2071.3572.6481.9314.09520 users2.4095.2132.1414.4782.7635.6824.2338.484

323 +	1.16 +	2.746 +	1.622 +	4.021 -
8 users	1.429 -	3.057 -	1.285 -	2.747 -	1.62 -	3.354 -	2.415 -	5.079 -
20 users	3.073 +	7.877 -	2.595 +	6.307 +	3.411 +	8.287 +	6.409 +	14.703 +

CPUs and Memories

Service CPU Utilization:

CPU Utilization gradually increases as the number of users increase to 20 but this behavior is similar to okapi-4.3.3

Image Added

Service Memory Utilization:

Memory Utilization is a little high for mod-circulation 105% but for all other modules, it is relatively stable across all test runs for all users.

Image Added

RDS CPU Utilization

RDS CPU Utilization is around 50% more compared to okapi-4.3.3

Image Added

Comparison okapi-4.5.2 vs okapi-4.6.1

okapi-4.6.1 is slower than okapi-4.5.2. Checkin is 3.66% slower and Checkout is 9.48% slower. See below comparison for 8 Users 30-minute test run.

Image Added

Results for okapi-4.6.1

From the response times below, okapi-4.6.1, checkin-checkout for 1 user is a little slower but for 5, 8, 20 users, checkin-checkout is much faster comparing to okapi-4.3.3.

Response Times Okapi-4.3.3

	Average (seconds)		50th %tile (seconds)		75th %tile (seconds)		95th %tile (seconds)
	Check-in	Check-out	Check-in	Check-out	Check-in	Check-out	Check-in	Check-out
1 user	0.94	2.158	0.885	2.017	0.969	2.177	1.198	2.906
5 users	1.126	2.574	1.025	2.339	1.211	2.79	1.77	4.007
8 users	1.313	2.948	1.177	2.61	1.487	3.274	2.195	5.045
20 users	3.252	7.492	2.681	6.355	3.605	8.313	7.061	15.747

Response Times Okapi-4.6.1

'+' means a performance improvement from okapi-4.3.3

'-' means a performance degradation from okapi-4.3.3

	Average (seconds)				50th %tile (seconds)		75th %tile (seconds)				95th %tile (seconds)
	Check-in	Check-in performance with okapi-4.3.3	Check-out	Check-out performance with okapi-4.3.3	Check-in	Check-out	Check-in	Check-in performance with okapi-4.3.3	Check-out	Check-out performance with okapi-4.3.3	Check-in	Check-out
1 user	1.041	-9.7%	2.332	-7%	0.957	2.139	1.06	-8.5%	2.369	-8.10%	1.378	3.394
5 users	1.057	+6.5%	2.374	+8.4%	0.978	2.176	1.133	+6.88%	2.532	+10.18%	1.524	3.624
8 users	1.277	+2.8%	2.814	+4.7%	1.144	2.512	1.44	+3.2%	3.074	+6.50%	2.112	4.718
20 users	2.374	+36.9%	5.927	+26.4%	2.137	5.246	2.716	+32.7	6.552	+26.87	4.188	9.426

CPUs and Memories

Service CPU Utilization:

Compared to okapi-4.3.3, CPU Utilization for okapi-4.6.1 around the same.

Image Added

Service Memory Utilization:

Compared to okapi-4.3.3, Service Memory Utilization for okapi-4.6.1 around the same.

Image Added

RDS CPU Utilization

RDS CPU Utilization is normal for 1, 5, and 8 Users. For 20 Users, the CPU is higher almost 95% but considering the large load, it is normal as well.

Image Added

8 Hours Longevity test run for 20 Users

Service CPU Utilization:

Okapi-4.6.1 consumes less CPU gradually from 1st hour into 8th hour. However, at the same time, mod-pubsub consumes more CPU by gradually increasing from 50% to almost 160%

Image Added

Service Memory Utilization:

Memory usage for okapi-4.6.1 and other modules is relatively constant and stable throughout the run. mod-circulation memory consumption increases to 125% and then stabilizes.

Image Added

Comparison okapi-4.3.3 vs okapi-4.6.1 (okapi metrics enabled)

Below results are for 8 Users, 30 minutes against Checkin-Checkout workflow.

Grafana Performance Dashboard

Okapi-4.6.1 is around 71% faster than Okapi-4.3.3. Okapi-4.6.1 can process more requests and still perform better. In 30 minutes test run, okapi-4.6.1 was able to process 25% more requests with an average request per second(RPS) is 40.

Okapi-4.3.3 Grafana performance dashboard:

Image Added

Okapi-4.6.1 Grafana performance dashboard:

Image Added

Checkin-Checkout API level comparison

For Okapi-4.6.1, Check-in is 71% faster and Checkout is around 65% faster.

Image Added

Log request/response comparison

For Okapi-4.6.1, Log request has improved from 3.16 second to 0.243 seconds. Log request is faster by 1200% faster. Log response has improved from 3.25 seconds to 0.266 seconds which is 1100% faster.

Okapi-4.6.1 can process more log request/response and at the same time be fast. Okapi-4.6.1 processed [211k(logRequest), 220k(logResponse)] vs Okapi-4.3.3 which processed [170k(logRequest), 177k(logResponse)].

Okapi-4.3.3 log request/response comparison:

Image Added

Okapi-4.6.1 log request/response comparison:

Image Added

Service CPU Utilization

Okapi-4.6.1 consumes less CPU and hence more efficient. Average CPU Utilization for okapi-4.6.1 is around 380% vs okapi-4.3.3 which is 600%.

Okapi-4.3.3 Service CPU Utilization:

Image Added

Okapi-4.6.1 Service CPU Utilization:

Image Added

Appendix

CIRC-1014

https://issuesfolio-org.folioatlassian.orgnet/browse/MODPATBLK-70

https://issuesfolio-org.folioatlassian.orgnet/browse/OKAPI-964

https://issuesfolio-org.folioatlassian.orgnet/browse/OKAPI-965

checkout-checkin-4.5.2-test-runs

Versions Compared

Old Version 13

New Version Current

Key

Results for okapi-4.5.2

CPUs and Memories

RDS CPU Utilization

Comparison okapi-4.5.2 vs okapi-4.6.1

Image Added

Results for okapi-4.6.1

CPUs and Memories

RDS CPU Utilization

8 Hours Longevity test run for 20 Users

Comparison okapi-4.3.3 vs okapi-4.6.1 (okapi metrics enabled)

Grafana Performance Dashboard

Checkin-Checkout API level comparison

Log request/response comparison

Service CPU Utilization

Appendix

Page Comparison

Versions Compared

Old Version 13

New Version Current

Key

Results for okapi-4.5.2

CPUs and Memories

RDS CPU Utilization

Comparison okapi-4.5.2 vs okapi-4.6.1

Image Added

Results for okapi-4.6.1

CPUs and Memories

RDS CPU Utilization

8 Hours Longevity test run for 20 Users

Comparison okapi-4.3.3 vs okapi-4.6.1 (okapi metrics enabled)

Grafana Performance Dashboard

Checkin-Checkout API level comparison

Log request/response comparison

Service CPU Utilization

Appendix