Skip to content

[fix] benchmark run with compose #666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 6, 2021
Merged

[fix] benchmark run with compose #666

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion benchmarks/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ docker-compose up
Then you can run the benchmark with:

```bash
docker-compose run ballista-client cargo run benchmark ballista --host ballista-scheduler --port 50050 --query 1 --path /data --format tbl
docker-compose run ballista-client bash -c '/tpch benchmark ballista --host ballista-scheduler --port 50050 --query 1 --path /data --format tbl'
```

## Expected output
Expand Down
2 changes: 0 additions & 2 deletions benchmarks/docker-compose.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,12 +41,10 @@ services:
ballista-client:
image: ballista:0.5.0-SNAPSHOT
command: "/bin/sh" # do nothing
working_dir: /ballista/benchmarks/tpch
environment:
- RUST_LOG=info
volumes:
- ./data:/data
- ../..:/ballista
depends_on:
- ballista-scheduler
- ballista-executor
Expand Down