Forum Discussion
Dataflow error for huge records - Evaluation resulted in a stack overflow
Hi curth,
I tested with much larger records. This is what I noticed in my localmachine. The highlighted value is the commit size.
Since it is not executing in dataflow and giving stack overflow error, could it be related to dataflow capacity?
I am using powerBI premium shared capacity. But unfortunately, I dont know the dataflow capacity set.
Actually the issue seems to due to the heavy function (get latest function) on the table having lakhs of records.
In the above post, I posted the commit size when I loaded single table in powerbi desktop. Now this image shows the commit size when I tried to do the same operation for three tables in powerbi desktop. And my CPU and memory hit the peak.
I also confirmed the memory thrashing in premium exceeded 80%.
Wondering if there is a better way to optimize get latest function?