@@ -41,17 +41,17 @@ To run the benchmarks it is necessary to have at least one Ballista scheduler an
4141To run the scheduler from source:
4242
4343``` bash
44- cd $BALLISTA_HOME /rust/ballista
45- RUST_LOG=info cargo run --release --bin scheduler
44+ cd $ARROW_HOME /rust/ballista/rust/scheduler
45+ RUST_LOG=info cargo run --release
4646```
4747
4848By default the scheduler will bind to ` 0.0.0.0 ` and listen on port 50050.
4949
5050To run the executor from source:
5151
5252``` bash
53- cd $BALLISTA_HOME /rust/ballista
54- RUST_LOG=info cargo run --release --bin executor
53+ cd $ARROW_HOME /rust/ballista/rust/executor
54+ RUST_LOG=info cargo run --release
5555```
5656
5757By default the executor will bind to ` 0.0.0.0 ` and listen on port 50051.
@@ -65,7 +65,8 @@ RUST_LOG=info RUSTFLAGS='-C target-cpu=native -C lto -C codegen-units=1 -C embed
6565To run the benchmarks:
6666
6767``` bash
68- cargo run benchmark --host localhost --port 50050 --query 1 --path $( pwd) /data --format tbl
68+ cd $ARROW_HOME /rust/ballista/rust/benchmarks/tpch
69+ cargo run --release benchmark --host localhost --port 50050 --query 1 --path $( pwd) /data --format tbl
6970```
7071
7172## Running the Benchmarks on docker-compose
@@ -87,7 +88,7 @@ docker-compose run ballista-client cargo run benchmark --host ballista-scheduler
8788
8889## Expected output
8990
90- The result of query 1 should produce the following output:
91+ The result of query 1 should produce the following output when executed against the SF=1 dataset.
9192
9293```
9394+--------------+--------------+----------+--------------------+--------------------+--------------------+--------------------+--------------------+----------------------+-------------+
0 commit comments