Inquiry: Impact of Merging Business Rules on System Performance

[Rakesh50]

Hi Community,

I'm seeking advice regarding the performance improvements from reducing the number of Business Rules (BRs) in our system. Currently, we have about 40 BRs, and we're planning to merge multiple BRs into one where they are the same filter conditions, execution order, and type (after/before).

We're wondering if this consolidation will indeed enhance system performance. During light house testing by our QA team, we've noticed suboptimal results, prompting us to consider refactoring our BRs. Can anyone provide insights or suggestions on this matter?

Thank you in advance for your assistance!

Rakesh T.

[Dr Atul G- LNG]

Hi @Rakesh50 

As you said, you tried and got some results, but my thought say dont merge all 40 in one go, its like keeping all eggs in 1 basket, one side it is good, as one place check but other hand it is tough as in future if need to change one line may impact whole BR.

What i can suggest , try to grab the low hanging fruits, BR which are not so common in use , merge and see the performace. 

[Rakesh50]

hi @Dr Atul G- LNG ,

We are not merging all BRs into one. We are merging the BRs only if they have the same execution order, type (before/update), insert/update operations, and identical filter conditions.

Our primary objective is to improve system performance. Will it improve the performance of page loading?

[Dr Atul G- LNG]

Hi @Rakesh50 

It is tough to say without making changes, as this is code /scripts and until unless we try we cant say it will be helpful or not.

Also now I have doubt it might be impact performance , as if we merge similar nature of BR , lets say my we merge 4 BR and now when i want that it execute , so system need to check code of all 3 BR line of code and then 4 , where without merge, system directly pick the 1 BR. 

So tough to say, but give a try one by one, test it , observe it for atleast 1- 1.5 months and then move to next merger.

[AshishKM]

Hi @Rakesh50 ,

The best way to list all BR ( matching condition ) and check what exactly they are doing. Merge all in one not a good idea at first place but if you found some redundent logic you can merge some related BR in single one but not all 40 in one. Also for peformance related, change the order , do not run all related BR with order =100. 

-Thanks,
AshishKM