ASAP Performance | Queuing Of Messages At SARM During Slowness
(Doc ID 2273651.1)
Last updated on JANUARY 25, 2019
Applies to:Oracle Communications ASAP - Version 7.0.1 and later
Information in this document applies to any platform.
ASAP performance | Queuing of messages at SARM during load test
Customer recently upgraded the code on the performance testing environment and observed that there was a performance decrease of the orders at ASAP tasks when orders were placed in bulk.
1. The following lines are observed in the SARM diagnostic log files :
SARMAS7.diag.030130:Stats: 293969927:3031 SRP Transaction 'WO Accept' Queued: 715.93s Complete: 0.08s Event 370477944
SARMAS7.diag.030130:Stats: 293969927:3031 SRP Transaction 'WO Startup' Queued: 716.00s Complete: 0.07s Event 370477945
SARMAS7.diag.030130:Stats: 293969927:3031 SRP Transaction 'WO Completion' Queued: 714.96s Complete: 0.07s Event 370477957
The messages are queued for almost 700 seconds here. This is usually less than 1 or 2 seconds. The time increases as the test progresses. The initial Queued times at the start of test are very normal : 0.00s to 0.2s.
2. The number of records in tbl_wrk_order is nearly 9 million.
3. There is a purge job that runs on the SARM database on this server. As this was scheduled, it used to run frequently in the past but was in a broken state for the last month. After observing the poor performance, customer rescheduled the job and ran it again on this database. The poor performance is observed even after the purge job had been executed.
As a comparison, a similarly configured ASAP production environment is working fine with much heavier load.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document