Versions Compared

Key

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

...

Bulk Edits - Establish a performance baseline for Items bulk updates PERF-406 in the Orchid release that has architectural changes that were implemented in UXPROD-3842. The goal is to make sure the performance did not deteriorate in comparison to Nolana release.  Some questions can help us to determine the performance and stability of the new Bulk Edits implementation:

...

Test report for Bulk Edits items-app functionality 2023-03-08. 

Orchid release works 30% faster for 10k items bulk editing than Nolana.

It is approximately the same stable as Nolana.

  • For 1 concurrent job 100 records can be edited in 1 min 9 s which is 3 times slower than in Nolana, 1000 records editing could be performed in approximately the same time as Nolana(2 min 40 s), and 10k records bulk editing is about 30% faster.
  • 10k records per user, 5 users simultaneously (50k records total) can be uploaded and edited in about 20 minutes which is about 8 min faster compared to Nolana (about 28 min).
  • The memory of mod-inventory-storage was high at 109% but stable (It was 109% even before the test). No memory leaks were found.
  • CPU for mod-users was up to 125% (5 concurrent jobs 10k records updating) increased compared to Nolana (was about 40% with the same configurations) Need to be investigated in further testing. For all other modules did not exceed 65% for all of the tests.
  • For all records number (100, 1k,10k), and 5 concurrent jobs - RDS CPU utilization did not exceed 60%.

...

More than 50% of jobs FAILED in about 28-33 min with the error "Connection reset (SocketException)".

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-334

From time to time Job FAILED with the error from the s3 bucket

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODBULKOPS-76

The high CPU usage of mod-users (up to 125% ) needs to be investigated.

Results

Test Runs

1# One (concurrent) Job
Number of recordsDurationComments
1001 min 9 s
10002 min 36 s
10k17 min 50 s
50k1 hour 58 min

or Error in about 28-33 min Connection reset (SocketException)

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-334

100kalways FAILD

Error in about 28-33 min Connection reset (SocketException)

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-334

...

"BARCODE". Records number per 1 userOrchid (Total Time)Nolana (Total Time)Morning Glory (Total Time)
1001 min 10 s18 sec25-27 sec
10002 min 57 s3 min4 min
10k20 min 20 s28 min30 min
25k

Results are not representative because of
Error in about 28-33 min Connection reset (SocketException)

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-334

1 hour 3 min50 min
50k

Results are not representative because of
Error in about 28-33 min Connection reset (SocketException)

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-334

about 2 hours for successful jobs.-

...

The memory of mod-inventory-storage was high at 109% but stable (It was 109% even before the test). No memory leaks were found.

...

The more concurrent jobs are running -the higher RDS CPU usage - it looks like it should handle up to 7 concurrent jobs without any issues. The maximum number of jobs will be investigated. 

Appendix

Infrastructure

PTF -environment ncp5 [ environment name] 

...