Order in SUM agregation parameters for performance

david.savarin

Hi hive mind,

I have a tricky question. Here we go :

• I have a target module with 3 custom dimension (A,B,C) + Time (Month)
• I have a source transaction module containing line Items with A, B, C list formarted and a date column and an amount column
• In my Target Module, I need to agregate the Source amount with A,B,C and month
• Is the order of the sum parameter used in the formula going to impact performance ?
• Where should be the Month SUM: parameter in the formula (beginning or end)
• For instance Source Module.Amount[SUM:A, SUM:B, SUM:C, SUM:Date) is the correct performance optimized formula (A,B,C is the order in the "applies to" dimension besides)

rob_marshall

@david.savarin

You know I am going to ask you this, but why is Time a line item in the source module? Is this transactional data that is being loaded from a data hub/other source system or is it something else entirely?

But to answer your question, yes, it does make a difference the way you are doing your mapping within the SUM. It is best to make sure it matches the Applies To of the Target module. As for Time, you can place that at the front of the back, I don't believe it makes that much difference but you can definitely test it using the new Calculation Effort column in the blueprint.

david.savarin

Thanks, i used the calc effort new feature to update calculations.

It works aligning sum order with applies to and put time last.

I ll have to test if does make a difference putting it in front.