Forum Discussion

Bubufun's avatar
Bubufun
Frequent Visitor
2 years ago

Optimizing DAX Calculation Efficiency and Resolving Memory Issues with WorkHourTemp Field

I have created a DAX field called WorkHourTemp, but the calculation process consumes too much memory. Once the data exceeds ten thousand records, it results in an 'out of memory' issue. Here is the ...
Need Help
lbendlin's avatar
lbendlin
Super User
2 years ago

First thing you want to do is disable auto date/time.  Your UTC column has a high cardinality as it is, and doesn't need that additional baggage.

 

but due to specific settings in each machine's sensors, identical timestamps never occur.

Yeah, no.

 

If the previous mV value is less than 1 within this interval, calculate the difference in UTC between the current and previous record, in hours to two decimal places.
If the previous mV change is greater than or equal to 1, do not calculate the time difference.
If the previous record is empty, or if Event = Clock-in or Clock-out, do not calculate the time difference.

Those are all rather ambiguous.  I don't see any empty records, for example.  What does "mV change"  mean?  Are you only ever looking for the rising slope?