Rating Ifw Pipeline Performance Is Degrading Over Time
(Doc ID 1148754.1)
Last updated on JUNE 30, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.0]
Information in this document applies to any platform.
In a production environment, the rating pipeline was working slower and slower every day. The performance was degrading a bit every day. We did not notice any sudden slowdown.
In February, the ifw was processing between 300 and 400 edrs per second; in July, it went down to 50 edrs/sec. When shutting down other programs in that server, the application started processing faster, up to 150 edrs/sec, but not the same as months ago. Nothing was changed in the server, the same applications were running as in February.
The user was planing to purge audit tables to see if the performance is increased (using purge_audit_tables.pl on these tables: au_purchased_product, au_product, au_service, au_profile, au_account, au_billinfo, au_deal, au_discount, au_bal_grp, au_group).
The ifw has started using more memory than before, and each day it used more to start.
Will the ifw need less memory to start with purging the audit tables?
This was the size (in records) of some audit tables:
au_purchased_product_t = 5,115,735
au_service_t = 6,039,088
au_profile_t = 2,807,454
Is there a threshold after which we should purge audit tables?
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