Overview

Bulk Edit - Establish a performance baseline for user status bulk updates. 

• How long does it take to export 100, 1000, 5000, 10k, and 100K records?
• Use it for up to 5 concurrent users.  
• Look for a memory trend and CPU usage
• Pay attention to any RTR token expiration messages and observe how/if BE is affected by expiring tokens. If needed set the Access token's expiration time to 300s or less to trigger the Access token's quick expiration. 

How long does it take to export 100, 1000, 10k, and 100K records?

• Can it be used with 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 

Appendix

Infrastructure

PTF -environment pcp1

• 11 m6g.2xlarge EC2 instances located in US East (N. Virginia)us-east-1
• 2 instances of db.r6.xlarge database instances, one reader, and one writer
• MSK tenant
  
  • 4 m5.2xlarge brokers in 2 zones

  • Apache Kafka version 2.8.0

  • EBS storage volume per broker 300 GiB

  • auto.create.topics.enable=true
  • log.retention.minutes=480
  • default.replication.factor=3

Modules memory and CPU parameters

Methodology/Approach

1. Item records update:
   1. Upload file with item barcodes 
   2. Click the Start bulk edit option in the Action menu and make the following changes:
      1. Set Temporary location to Clear field
      2. Set Permanent location to < to the value available on test environment>
      3. Set Status to Unknown
      4. Set Temporary loan type to Clear field
      5. Set Permanent loan type to < to the value available on test environment>
      6. Add Administrative note by adding text: "This is a new administrative note"
      7. Add Action note by adding text: "This is a new action note"
      8. Suppress from discovery (set the value to true)
   3. Confirm the changes
   4. Commit the changes
   5. Verify the changes are correct
   6. Download the file with updated records
   7. Download the file with errors (if applicable)

Test 1: From UI run Bulk edit job with changes above. Run up to 5 concurrent processes in new browser tabs. Check if after the update files are downloaded successfully. 

Test 2: Manually tested 100k+50k+1 record files DI started simultaneously on every 3 tenants (9 jobs total).

Test 3: Run CICO on one tenant, DI jobs 3 tenants, including the one that runs CICO. Start the second job after the first one reaches 30%, and start another job on a third tenant after the first job reaches 60% completion. CICO: 20 users, DI file size: 25k

Test 4. To define the optimal value for RECORDS_PER_SPLIT_FILE(500, 1K, 2K, 5K) data-import job with PTF-Create-2 profile were run for 25K for 1 tenant simultaneously, for 2 tenants and for 3 tenants.