Skip to content
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.

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

Document how to run TPC-H benchmarks in Kubernetes #949

Open
andygrove opened this issue May 16, 2021 · 0 comments
Open

Document how to run TPC-H benchmarks in Kubernetes #949

andygrove opened this issue May 16, 2021 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@andygrove
Copy link
Member

andygrove commented May 16, 2021

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I had to spend time figuring out how to deploy the benchmarks to Kubernetes, so I plan on documenting this.

Describe the solution you'd like

  • Dockerfile for packaging up benchmarks
  • Example YAML for running as a pod.

Here is the YAML I have been using:

apiVersion: v1
kind: Pod
metadata:
  name: tpch
  namespace: default
spec:
  containers:
    - image: andygrove/ballista-arm64
      command: [ "/tpch",
                 "benchmark",
                 "--query=1",
                 "--path=/mnt/tpch/parquet-sf100-partitioned/",
                 "--format=parquet",
                 "--concurrency=24",
                 "--iterations=1",
                 "--debug",
                 "--host=ballista-scheduler",
                 "--port=50050"]
      imagePullPolicy: Always
      name: tpch
      volumeMounts:
          - mountPath: /mnt/tpch/parquet-sf100-partitioned/
            name: data
  restartPolicy: Never
  volumes:
    - name: data
      persistentVolumeClaim:
        claimName: data-pv-claim

Describe alternatives you've considered
None

Additional context
None

@andygrove andygrove added documentation Improvements or additions to documentation enhancement New feature or request labels May 16, 2021
@andygrove andygrove self-assigned this May 16, 2021
@jorgecarleitao jorgecarleitao removed the enhancement New feature or request label May 16, 2021
@andygrove andygrove removed their assignment May 2, 2022
@andygrove andygrove transferred this issue from apache/datafusion Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants