After one week of going through every BO rule and make optimizations (based on the video Support supplied) I'm blown away with the positive results. The Log viewer was the major tool to gauge each change. Just for example, before making ONE optimization, saving a Customer BO would trigger so many rules to "Execute". Look at the size of the scroll bar, to give you an idea how many other BO rules were being executed. This is before optimization
This is after ONE optimization. The scroll bar is so much smaller, but then they're only evaluation lines and nor execution.
A complex "Replication" process execution went from 94 seconds to 42 seconds to 7 seconds. That's over 13 times faster and CPU and DISK I/O saving.
During the 94 seconds, CPU was 41% and DISK I/O was 98%
During the 7 seconds, CPU spiked to 21% and DISK I/O Spiked to 40% but went down to 5%.
Do yourself a huge favor and optimize your Aggregate and cross reference rules.
Hope this helps.
Thank you support for the Performance Video.
Update: When it comes to Aggregate functions, think real hard to see if you can remove these from BO rules to on-demand process. When you have multilevel relationships and each parent keeps track of # of children and it's put in a BO rule, that takes a huge toll on the system. I made lots of changes here and it paid off.
