Skip to end of banner
Go to start of banner

Bulk Edit Items App report [Orchid] 08/03/2023

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »



Overview

Bulk Edit - Establish a performance baseline for Items bulk updates PERF-406

  • How long does it take to export 100, 1000, 10k, and 100K records?
  • Use it for up to 5 concurrent users.  
  • Run consecutively four jobs editing 10k  item records
  • Run simultaneously four jobs editing 10k item records
  • Look for a memory trend and CPU usage

Summary 

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

  • 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. No memory leaks were found.
  • CPU for mod-users was up to 125% (5 concurrent jobs 10k records updating). 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%.

Results

Test Runs

1#
1 concurrent job
Number of recordsDurationComments
1001 min 9 s
10002 min 36 s
10k17 min 50 s
50k1 hour 58 minor Error in about 28-33 min Connection reset (SocketException)
100kalways FAILDError in about 28-33 min Connection reset (SocketException)
2#

Items App 10k records 3, 4, and 5 concurrent jobs

10k records for each job
Number of concurrent jobsDuration
117 min 50 s
318 min 50 s
419 min 10 s
520 min 20 s
3#

Items App 5 concurrent jobs

5 concurrent jobsOrchidNolanaMorning Glory

"BARCODE". Records number per 1 user


Total time
Total timeTotal time
1001 min 10 s18 sec25-27 sec
10002 min 40 s3 min4 min
10k20 min 20 s28 min30 min
25kResults are not representative because of
Error in about 28-33 min Connection reset (SocketException)
1 hour 3 min50 min
50kResults are not representative because of
Error in about 28-33 min Connection reset (SocketException)
about 2 hours for successful jobs.-

 * "-" test was not performed due to errors that occurred

4#

consecutively four jobs editing 10k  item records

Job #Job duration (run 2)Job duration (run 1)
117 min 47 s18 min 49 s
217 min 53 s18 min 26 s
317 min 45 s20 min 44 s
418 min 5 s

ERROR occurs:

We encountered an internal error. Please try again. (Service: S3, Status Code: 500, Request ID: 5W7F75FMHHH3KDWT, Extended Request ID: 36K8tkhFQHS1Mjt7sZc4jYrBduBWO/psei+33ZIIOnhrytq7Eie3mjDALtBplhZxSJv4CfrZpnw8Z6nqmz03ZB7b3yiRdecyXfZ/ZtEmN4g=) (S3Exception)

Memory usage

For all test runs

The memory of mod-inventory-storage was high at 109% but stable. No memory leaks were found.


CPU utilization





RDS CPU utilization






  • No labels