pin_inv_accts Performance Issue (Doc ID 2788335.1)

Last updated on FEBRUARY 24, 2023

Applies to:

Symptoms

Customer have initiated invoicing(pin_inv_accts) for 100K accounts and captured the stats for 50K and stopped the Invoicing as performance with 9.46 Transaction Per Second(TPS) .

Start time of the script(pin_inv_accts) for 100k accounts : Fri Apr 30 22:02:00 JST 2021
End time of the script while completing 50K accounts      : Fri Apr 30 23:28:05 JST 2021

After Enabling the stack for 5k accounts:
start time : Fri Apr 30 23:37:23 JST 2021
End Time : Fri Apr 30 23:45:35 JST 2021

In both the cases achieved around 10 TPS.

STEPS: 
Followings are the additional three test cases executed (ran pin_inv_accts). 
Customer have disabled the customization from cm pin.conf and performed the Invoicing with Different threads and below is the observation

1) With 50- threads for 50k account, getting PIN_ERR_DM_CONNECT_FAILED error and achieved around 80 TPS with out of the box(OOB)  code.

cm pin.conf  :

- dm extra_search 1     

1.pin_inv pin.conf :

1) With 50- threads for 50k account , getting DM_CONNECT_FAILED  and achieved around 80 TPS with OOB code 

- pin_mta children 50
- pin_mta per_batch 2000
- pin_mta per_step 10000
- pin_mta fetch_size 100000

2) With Children 20 Thread for 50k account, getting PIN_ERR_DM_CONNECT_FAILED. We achieved around 80 TPS with OOB code.
- pin_mta children 20
- pin_mta per_batch 500
- pin_mta per_step 10000
- pin_mta fetch_size 100000

3)With Children 10 Thread for 50k account. achieved around 50 TPS with OOB code.
- pin_mta children 10
- pin_mta per_batch 500
- pin_mta per_step 10000
- pin_mta fetch_size 100000

Customer did not achieve expectation with the minimal threads. T

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.