My Oracle Support Banner

Low Performance of CustomerSearch Module (Doc ID 2344060.1)

Last updated on SEPTEMBER 06, 2023

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.

Purpose

 On : 7.4.0.7.0 version, Pipeline Manager

In a customer system, on enabling the instrumentation (using "kill -s USR1 <Pipeline_PID>" ), it seems that the most amount of time is consumed by CustomerSearch (FCT_Account) module. Below is the example snippet from the pipeline log, showing the statistics related to CustomerSearch module:

Questions and Answers

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
Purpose
Questions and Answers
 Are the functions starting with "DB:" related to data processing from database ?
 Are the functions starting with "FT:" related to in-memory data processing ?
 By adding the time spent in all the DB: and FT: functions, is the total value supposed to be the same time as the global time displayed for CustomerSearch Module (for example, 353172024 in this example ) ?
 What are those different functions (DB: and FT:) used inside customerSearch ?
 One can see that there are two numbers for the statistics (ex: FT:Parse_166731,111014971); here the first number seems to be the number of CDRs that went through the module, is this correct ?
 Any suggestions for performance improvement for this Module ?


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