Conversation
comphead
left a comment
There was a problem hiding this comment.
Thanks @gabotechs I think it shouldn't be there. by default the script checks for datafusion-benchmarks repo here https://github.com/apache/datafusion-benchmarks/tree/main/tpcds/data/sf1 and there is no tpcds-sf1.
you can specify your own DATA_DIR like
export DATA_DIR=../../datafusion-benchmarks/tpcds/data/sf1/
and then run tpcds benchmarks
|
🤔 Are you sure? I get the impression that this is why the benchmark run commands are failing Also, note how the https://github.com/apache/datafusion/blob/main/benchmarks/bench.sh#L633 |
|
I just checked for #19635 the TPCDS benchmark the commands provided in |
|
Ok, I see what happened here:
IMO it would be nicer if In fact, I'd bet the intention behind this code here https://github.com/apache/datafusion/blob/main/benchmarks/bench.sh#L644-L646 is that it works that way, as it's explicitly extracting the contents to However happy to follow your lead here, I can survive setting up an extra env variable. |
That would be real nice but data generation is tricky for TPCDS so we rely on pregenerated data in |
BTW @clflushopt and I are working on a solution to that -- sneak peek: |
## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes apache#123` indicates that this PR will close issue apache#123. --> - Closes #. ## Rationale for this change <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> Running ` ./bench.sh run tpcds` with a freshly created `./bench.sh data tpcds` fails with the following error: ``` Please prepare TPC-DS data first by following instructions: ./bench.sh data tpcds ``` This PR fixes it ## What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> Fixes the `TPCDS_DIR` variable in `run_tpcds` ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> just benchmark scripts ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. --> no need
Which issue does this PR close?
Rationale for this change
Running
./bench.sh run tpcdswith a freshly created./bench.sh data tpcdsfails with the following error:This PR fixes it
What changes are included in this PR?
Fixes the
TPCDS_DIRvariable inrun_tpcdsAre these changes tested?
just benchmark scripts
Are there any user-facing changes?
no need