Skip to content

Setup TorchBench in Docker #158613

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

Open
wants to merge 28 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
Update
[ghstack-poisoned]
  • Loading branch information
huydhn committed Jul 17, 2025
commit 30c21cb1b854480090bc4fdbcbab5a394b7eb6b4
1 change: 1 addition & 0 deletions .github/workflows/inductor-perf-test-nightly-h100.yml
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,7 @@ jobs:
{ config: "inductor_torchbench_perf_cuda_h100", shard: 9, num_shards: 9, runner: "linux.aws.h100" },
]}
selected-test-configs: ${{ inputs.benchmark_configs }}
build-additional-packages: "vision audio text fbgemm torchao"
secrets: inherit

test-periodically:
Expand Down
3 changes: 3 additions & 0 deletions .github/workflows/inductor-perf-test-nightly.yml
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,8 @@ jobs:
needs: get-label-type
with:
runner_prefix: "${{ needs.get-label-type.outputs.label-type }}"
# Every bit to make perf run faster helps
runner: linux.12xlarge.memory
build-environment: linux-jammy-cuda12.8-py3.10-gcc9-sm80
docker-image-name: ci-image:pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc9-inductor-benchmarks
cuda-arch-list: '8.0'
Expand All @@ -112,6 +114,7 @@ jobs:
{ config: "cachebench", shard: 2, num_shards: 2, runner: "linux.aws.a100" },
]}
selected-test-configs: ${{ inputs.benchmark_configs }}
build-additional-packages: "vision audio text fbgemm torchao"
secrets: inherit

test-nightly:
Expand Down
1 change: 1 addition & 0 deletions .github/workflows/inductor-periodic.yml
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,7 @@
build-environment: linux-jammy-cuda12.8-py3.10-gcc9-sm80
docker-image: ${{ needs.linux-jammy-cuda12_8-py3_10-gcc9-inductor-smoke-build.outputs.docker-image }}
test-matrix: ${{ needs.linux-jammy-cuda12_8-py3_10-gcc9-inductor-smoke-build.outputs.test-matrix }}
build-additional-packages: "vision audio text fbgemm torchao"

Check failure on line 138 in .github/workflows/inductor-periodic.yml

View workflow job for this annotation

GitHub Actions / lintrunner-noclang / linux-job

ACTIONLINT [workflow-call]

input "build-additional-packages" is not defined in "./.github/workflows/_linux-test.yml" reusable workflow. defined inputs are "aws-role-to-assume", "build-environment", "dashboard-tag", "disable-monitor", "docker-image", "monitor-data-collect-interval", "monitor-log-interval", "s3-bucket", "sync-tag", "test-matrix", "timeout-minutes", "use-gha"
secrets: inherit

linux-jammy-cpu-py3_9-gcc11-periodic-dynamo-benchmarks-build:
Expand Down
3 changes: 2 additions & 1 deletion .github/workflows/test-h100.yml
Original file line number Diff line number Diff line change
Expand Up @@ -37,14 +37,15 @@ jobs:
needs: get-label-type
with:
runner_prefix: "${{ needs.get-label-type.outputs.label-type }}"
runner: "linux.12xlarge"
runner: linux.12xlarge.memory
build-environment: linux-jammy-cuda12.8-py3.10-gcc11-sm90
docker-image-name: ci-image:pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc11
cuda-arch-list: '9.0'
test-matrix: |
{ include: [
{ config: "smoke", shard: 1, num_shards: 1, runner: "linux.aws.h100" },
]}
build-additional-packages: "vision audio text fbgemm torchao"
secrets: inherit

linux-jammy-cuda12_8-py3_10-gcc11-sm90-test:
Expand Down
Loading
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy