You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Respect DATA_DIR location for sql benchmarks (#21961)
## 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#123` indicates that this PR will close issue #123.
-->
- Closes #.
## Rationale for this change
Currently if DATA_DIR is set for bench.sh it is not respected for sql
benchmarks and defaults to benchmarks/data
## What changes are included in this PR?
Updated tpch benchmarks to respect DATA_DIR defaulting to 'data' (in
benchmarks/)
## Are these changes tested?
Yes, unit test + manual testing.
## Are there any user-facing changes?
No.
Copy file name to clipboardExpand all lines: benchmarks/sql_benchmarks/README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,9 +68,10 @@ The SQL benchmarking tool uses the following environment variables:
68
68
| BENCH_QUERY | A query number to run. |
69
69
| BENCH_PERSIST_RESULTS | true/false to persist benchmark results. Results will be persisted in csv format so be cognizant of the size of the results. |
70
70
| BENCH_VALIDATE | true/false to validate benchmark results against persisted results or result_query's. If both `BENCH_PERSIST_RESULTS` and `BENCH_VALIDATE` are true, persist mode runs and validation is skipped. |
71
+
| DATA_DIR | Root directory for benchmark data loaded by SQL benchmark files. When unset, uses `data` (relative to the benchmarks/ directory). |
71
72
| SIMULATE_LATENCY | Simulate object store latency to mimic remote storage (e.g. S3). Adds random latency in the range 20-200ms to each object store operation. |
72
73
| MEM_POOL_TYPE | The memory pool type to use, should be one of "fair" or "greedy". |
73
-
| MEMORY_LIMIT | Memory limit (e.g. '100M', '1.5G'). If not specified, run all pre-defined memory limits for given query if there's any, otherwise run with no memory limit. ||
74
+
| MEMORY_LIMIT | Memory limit (e.g. '100M', '1.5G'). If not specified, run all pre-defined memory limits for given query if there's any, otherwise run with no memory limit. |
74
75
75
76
Example – Run the H2O window benchmarks on the 'small' sized CSV data files:
0 commit comments