My Oracle Support Banner

Low Performance of CustomerSearch Module (Doc ID 2344060.1)

Last updated on OCTOBER 09, 2019

Applies to:

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


 On : version, Pipeline Manager

Some queries are answered in this article around the below scenario :

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:

ifw.Pipelines.PPL_RATE1_CDR.Functions.Processing.FunctionPool.CustomerSearch.Module_167560, 353172024
INF_PROC_TIME_STATISTICS | Plugin processing time statistics:
DB:AccountProcessingTime_14, 1167645
DB:AccountProfileUpdateProcessingTime_14, 973
DB:AccountProfileUpdateQuery_BulkReadTime_14, 754972
DB:AccountQuery_BulkReadTime_14, 1165745
DB:PurchasedDiscountUpdate_10, 350164
DB:PurchasedProductUpdate_3, 209182
DB:ServiceOrderedBalanceGroupProcessingTime_1, 77590
DB:ServiceProcessingTime_2, 204840
DB:ServiceProfileUpdateProcessingTime_2, 269
DB:ServiceProfileUpdateQuery_BulkReadTime_2, 154015
DB:ServiceQuery_BulkReadTime_2, 204674
FT:CustomerASearch_70, 1898728
FT:CustomerBSearch_70, 1148630
FT:EdrSetDate_70, 267
FT:EdrSetup_70, 678

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
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.