Last updated on JULY 10, 2017
Applies to:Oracle Retail Predictive Application Server - Version 13.4.1 and later
Information in this document applies to any platform.
In Oracle Retail Predictive Application Server (RPAS) applications, it is observed that running a mace rule of type "A=B" may take considerably more time to execute than running A=0 and then A=B.
Consider a scenario in which both A and B are boolean (SKU_STR). If A is already populated, mace "A=B" will take longer to "loop over destination cells”, even if B is empty. It seems that the process of “looping over destination cells” (as indicated in processing logs) for "A=B"-type rules could have significant impact on system performance. The performance impact depends strongly on logical size.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms