Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Grafana dashboard - http://carrier-io.int.folio.ebsco.com/grafana/d/q69rYQlik/jmeter-performance?orgId=1&var-percentile=95&var-test_type=baseline&var-test=circulation_checkInCheckOut&var-env=int&var-grouping=1s&var-low_limit=250&var-high_limit=700&var-db_name=jmeter&var-sampler_type=All&from=1624636077093&to=1624640056950

 

Hotfix-2

Data Import

Test

Profile

Load

Duration

StatusI | H | I | SRS Marc

Job Id

Results/Notes

1.

Create import 25K (lone job)

25K

06/28 4:29 PM - 5:45 PM EDT - 1 hour 16 minutes

Completed with Error24950 | 24950 | 24950 | 249501090

Job failed to create all records;

kafka.consumer.max.poll.records=10

2.Create import 25K (lone job)25K06/29 2:05PM - 3:15 PM EDT - 1 hour 10 minutesCompleted25000 | 25000 | 25000| 250001093Created all records as expected. There was one sudden spike in the mod-inventory CPU.
3. Create import 25K (lone job)25K06/29 3:31PM - 4:30 PM EDT - 1 hour 1 minuteCompleted25000 | 25000 | 25000| 250001094

kafka.consumer.max.poll.records=10

Created all records as expected. No spikes seen.

4.Create import 25K (lone job)25K

06/29 17:35 - 18:23 EDT

48 minutes

Completed25000 | 25000 | 25000| 250001095

kafka.consumer.max.poll.records=10

Created all records as expected. No spikes seen.

5.Create import 50K (lone job)50K

06/29 22:51 UTC -

06/30 00:52 UTC

- 2 hours

Completed with Error50000 | 50000 | 49999 | 500001096

kafka.consumer.max.poll.records=10

Job stuck at 99%. Huge mod-inventory CPU spike midway (13 minutes) after 8 minutes of very low activities. events_cache spiked multiple times.

6.Create import 25K (with 20 users checkin/out)25K

06/30 03:56 UTC - 

06/30 04:49 UTC

53 minutes

Completed25000 | 25000 | 25000| 250001097

kafka.consumer.max.poll.records=10

7.Create import 25K (with 40 users checkin/out)25K06/30 4:41 PM UTC - 5:16 PM UTC -
  | |
35 minutesCompleted25000 | 25000 | 25000| 250001098

kafka.consumer.max.poll.records=10

No spikes. Okapi CPU utilization is high around 220% because checkin-checkout also running in the background.


Checkin-Checkout as background for DI above

DI Test# from aboveUsers
Req/sMin50th pct75th pct95th pct99th pctMaxAverageLatencyGrafana dashboard linkResults/Notes
6.20Total Check-in19.4950.3561.3971.9573.8315.99910.341.6953.4
6/29/2021 11:55PM-00:55AM EDT
High CPU utilization for Okapi 180% which is normal for 20 Users
Total Check-out60.6571.3263.034.0228.20212.92431.5393.6697.076
7.40Total Check-in28.5090.4132.7063.9717.91110.88319.2223.3546.5786/30/2021 12:20PM-1:40PM EDTHigh CPU utilization for Okapi 245% which is normal for 40 Users
Total Check-out86.3831.6696.1118.41717.41527.23553.7617.55114.468



Checkin-Checkout Standalone

TestUsers
Req/sMin50th pct75th pct95th pct99th pctMaxAverageLatencyGrafana dashboard linkResults/Notes
1.20Total Check-in24.7550.3260.8071.0391.5512.28413.6080.8911.4796/28/2021 2:42PM-3:50PM EDTHigh CPU utilization for Okapi 140% which is normal for 20 Users
Total Check-out75.7331.2351.9262.2283.1724.75112.9052.0813.014
2.40Total Check-in36.5290.3491.7242.3564.6756.74613.1362.0614.026/30/2021 10:14AM-11:22AM EDTHigh CPU utilization for Okapi 250% which is normal for 40 Users
Total Check-out109.91.444.0375.34610.50815.76532.9524.8448.978

...