Rule Performance Tuning

[tomok]

We are having both actual & forecasted data in the cube. For actualised weeks, data will be imported from the ERP system. For forecasted weeks, it will be computed (carried from week's inventory)
For inventory, I cant think of any way to "downsize" the rule/feeder. Hence am looking at Sales computation. If I put a IF to check on the year, will this shorten the feeder time?

Do you have a version dimension or something like that to delineate between Actual and Forecast. If so, why have you not referenced that in this rule?

Code: Select all

['Qty'] =>['Sales'];

There usually is no need to feed Actuals because they are generally static numbers. The above feeder statement is going to feed both Actual and Forecast.

[beek]

Seem I can try out what Steve suggested. Let me try out few rules, and see if the memory consumption as well as the cube loading time is smaller.
To Tomok,
There's Setting cube controls whether has the week turns actualised or not.

[Steve Rowe]

Beeks,
Tomoks point is a good one.

Normally in the actual part of s system sales would be loaded data.

In the planning side it could be ruled as price*quantity

So Tomok is querying if your Qty=>sales feeder should be active across all versions.

Cheers