Skip to content

Conversation

@ArkashaJavelin
Copy link
Contributor

Which issue does this PR close?

Closes #4134

Rationale for this change

See #4134

Are these changes tested?

Are there any user-facing changes?

object_store = "0.5.0"
parquet = "26.0.0"
parquet-test-utils = { path = "../parquet-test-utils/" }
parquet-test-utils = { path = "../parquet-test-utils/", version = "0.1.0" }
Copy link
Member

Choose a reason for hiding this comment

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

Another issue is that we don't publish parquet-test-utils so we still can't publish this crate. This dependency is used in the parquet_filter_pushdown benchmark and not in tpch. I wonder if we should consider re-organizing these benchmarks into individual crates.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, I agree there is some sort of impedance mismatch with the benchmarks at the moment (like are they something we ever want to run outside a source checkout) 🤔

Copy link
Member

@andygrove andygrove left a comment

Choose a reason for hiding this comment

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

object_store = "0.5.0"
parquet = "26.0.0"
parquet-test-utils = { path = "../parquet-test-utils/" }
parquet-test-utils = { path = "../parquet-test-utils/", version = "0.1.0" }
Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, I agree there is some sort of impedance mismatch with the benchmarks at the moment (like are they something we ever want to run outside a source checkout) 🤔

@alamb alamb merged commit 18c6a0b into apache:master Nov 8, 2022
@ursabot
Copy link

ursabot commented Nov 8, 2022

Benchmark runs are scheduled for baseline = 2a834d1 and contender = 18c6a0b. 18c6a0b is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update release scripts to support datafusion-benchmarks

4 participants