Malthe
Valued Contributor II

@Ashwin_DSA the job does not scan terabytes of data, all of that is pruned away (see the screenshot); it actually reads just 28 GB of data.

But again, the time is not accounted for, despite the user interface saying that the executions are shown in aggregated time as well. It just doesn't match. And there's also no way to debug this–you simply can't see where the time is spent.