Re: Strange WholeStageCodegen UI values

2020-07-10 Thread Michal Sankot
Hey guys, Thanks for insights. Bobby, I see that it guesses those values from run time of the whole task. But as the whole task took 6.6 minutes, how can it come up with 7.27 hours? Sean, yes there is a data skew. One task taking tens of minutes while other take tens of seconds. What gave it

Re: Strange WholeStageCodegen UI values

2020-07-09 Thread Sean Owen
It sounds like you have huge data skew? On Thu, Jul 9, 2020 at 4:15 PM Bobby Evans wrote: > > Sadly there isn't a lot you can do to fix this. All of the operations take > iterators of rows as input and produce iterators of rows as output. For > efficiency reasons, the timing is not done for

Re: Strange WholeStageCodegen UI values

2020-07-09 Thread Bobby Evans
Sadly there isn't a lot you can do to fix this. All of the operations take iterators of rows as input and produce iterators of rows as output. For efficiency reasons, the timing is not done for each individual row. If we did that in many cases it would take longer to measure how long something