Overview

Bulk Edits - Establish a performance baseline for combined bulk updates PERF-480 in the Orchid release that has architectural changes that were implemented in UXPROD-3842. The goal is to make sure that bulk edits can be performed simultaneously. 

• How long does it take to export 100, 1000, 2500, 5000 records?
• Use it for up to 5 concurrent users.  
• Look for a memory trend trnend and CPU usage

Summary.

Test report for Bulk Edits users-app functionality 2023-09-15. 

• 5k records per user, 5 users simultaneously (25k records total) can be uploaded in about 6 min 13 seconds, 
  Possible job duration degradation compared to NOLANA realese is caused by adding of new mod-bulk-operation module and by fully changing of bulk-edit architecture.
  
• The files with identifiers should be strictly determined.
• The memory of all modules during the tests for 5000 records with 5 parallel was stable, the memory gap in Figure 1 was caused by restarting several modules before DI job run. 
• Instance CPU usage 
  • maximal value for text 4VU (0.1-1-2.5k-5k) was 26%
  • maximal value for text 5VU (0.1-1-2.5k-5k) was 27%
• Service CPU usage for test 5VU (0.1-1-2.5k-5k) 
  • CPU of mod-bulk-operations 126%, for all other modules, did not exceed 22%. 
• RDS CPU utilization did not exceed 43% for 5jobs 5000 records and 34% for 4jobs  5k.

Recommendations & Jiras

For further testing Users' bulk editing can be performed with 10k records

Test Runs

Total processing time of upload and edit - commit changes. Units =minutes:seconds

...

(*2) Index 546 out of bounds for length 13 (ArrayIndexOutOfBoundsException)

(*3) Was running as a separate test to avoid duplication of input data

Comparison with previous results

Possible job duration degradation caused by adding of new mod-bulk-operation module and by fully changing of bulk-edit architecture.

Memory usage

The time range marked with # Several modules were restarted and then data import jobs were running on the environment environment (DI jobs were not part of Bulk Edits testing). 

Memory usage during the testing with 1-5 concurrent and  100-1000-2500-5000 records

Image RemovedImage Added

Memory usage during the testing with 2-5 concurrent and 5000 records

...

Memory usage for the same time range as Figure 2the figure below, but only involved services were selected.

Instance CPU utilization

Image RemovedImage Added

CPU instance utilization for 1 up to 5 Vu with 100-1000-2500-5000 records

 The test 5VU(0.1-1-2.5k-5k) was restarted because there were in the input data(Barcodes duplication)

Image RemovedImage Added

CPU instance utilization for 2 up to 5 Vu with 5000 records

Service CPU utilization

Image RemovedImage Added

CPU instance utilization for 1 up to 5 Vu with 100-1000-2500-5000 records

Image RemovedImage Added

CPU instance utilization for 1 2 up to 5 Vu with 100-1000-2500-VU with 5000 records

RDS CPU utilization

For all tests - RDS CPU utilization exceeds 40% (for tests with 5k user records). For the tests with 2500 user records did not exceed 27%.

Database connections

Image RemovedImage Added

Errors in logs during testing

(*1) Duplicate barcodes in CSV input data, 1200 out of 2500 records were processed

(*2) Index 546 out of bounds for length 13 (ArrayIndexOutOfBoundsException)

Appendix

Infrastructure

PTF -environment ncp5 [ environment name] 

...

Modules memory and CPU parameters: