Split DAX calculation steps to enhance memory utilization

An advantage of DAX measures over calculated columns is that they respond to user interaction. As such, you may be inclined to allocate all calculation logic into measures when there is a need to respond to slicer selection, for example.

From a pure performance point of view, this may not always be optimal however. Take the following example, in which a DAX developer intends to develop a metric for 'most current sales amount' per product (really, the last non empty sales amount per product). Using Adventure Works, you can see that each product may have different 'last non empty dates':