Skip to content

Conversation

@jorgecarleitao
Copy link
Member

The benchmarks were only benchmarking planning, not execution, of the plans. This PR fixes this.

@jorgecarleitao
Copy link
Member Author

FYI @andygrove , as 2.0.0' benchmarks not benchmarking anything atm :/

@github-actions
Copy link

Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR also changes some of the batch sizes -- which seems reasonable.


// display the relation
for _batch in results {}
rt.block_on(df.collect()).unwrap();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 this is the major change, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, the block is pick up the task. We also benchmark creating a runtime itself, but that was a very small compared to the task itself, so I left it there.

@andygrove andygrove closed this in c5280a5 Oct 13, 2020
kszucs pushed a commit that referenced this pull request Oct 19, 2020
The benchmarks were only benchmarking planning, not execution, of the plans. This PR fixes this.

Closes #8452 from jorgecarleitao/bench

Authored-by: Jorge C. Leitao <jorgecarleitao@gmail.com>
Signed-off-by: Andy Grove <andygrove@nvidia.com>
@jorgecarleitao jorgecarleitao deleted the bench branch October 28, 2020 04:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants