Splitter Pipeline Performance Issue In Production
(Doc ID 1399433.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.1 [Release 7.2.1]
Information in this document applies to any platform.
In a customers production system, the splitter pipeline's performance has degraded from few seconds/CDRs to several minutes/CDRs, which prevents rating process to be executed smoothly.
- After going live recently, it is now being observed that the splitter pipeline processing has become very slow compared to previous days' performance. It used to process a couple of thousand CDRs in few seconds , but now it takes few minutes to process the same number of CDRs
- The splitter pipeline's purpose is to split the incoming CDRs and direct them to the corresponding rating pipeline ( there are multiple rating pipelines )
- The splitting is done based on the balance group of the parent account , of the sharing group. So all such CDRs pointing to the same balance group are routed to the same pipeline.
From the awr reports of the database, it was noticed that the pipeline reads profile data from the database during rating. There are 500K accounts migrated that have the profile object modified lately. After starting pipeline and processing the CDRs, old records are causing pipeline to read older audit profile records. In this context, there is a need to understand which field of the au_profile_t table is used by the pipeline in order to verify the validity of the audit record kept in the pipeline memory. We saw that the sql queries are reading effective_t, valid_from_t.
How to address the performance issue ?
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