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.

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

Jump to bottom

Switch from w7900 to using any persistent cache runner for CPU. #18322

Merged
merged 3 commits into from
Aug 22, 2024
Merged

Switch from w7900 to using any persistent cache runner for CPU. #18322

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2695e97
switch to persistent cache
saienduri Aug 21, 2024
05c0222
more descriptive runs-on accounting for possible future windows runners
saienduri Aug 21, 2024
12ee997
Update .github/workflows/pkgci_regression_test.yml
saienduri Aug 21, 2024
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
8 changes: 6 additions & 2 deletions .github/workflows/pkgci_regression_test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,11 @@ jobs:
# CPU
- name: cpu_llvm_task
models-config-file: models_cpu_llvm_task.json
runs-on: nodai-amdgpu-w7900-x86-64
runs-on:
- self-hosted # must come first
- persistent-cache
- Linux
- X64

# AMD GPU
- name: amdgpu_rocm_mi250_gfx90a
Expand Down Expand Up @@ -234,7 +238,7 @@ jobs:
- name: cpu_llvm_task
models-config-file: models_cpu_llvm_task.json
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mi250:

============================== slowest durations ===============================
597.91s call     shark-test-suite-models/sdxl/test_unet.py::test_run_unet_cpu
292.26s call     shark-test-suite-models/sdxl/test_vae.py::test_run_vae_cpu
38.20s call     shark-test-suite-models/sdxl/test_unet.py::test_compile_unet_cpu
17.20s call     shark-test-suite-models/sdxl/test_clip.py::test_compile_clip_cpu

https://github.com/iree-org/iree/actions/runs/10498668335/job/29084321533#step:7:126

😬

might be an improvement over the w7900 if we at least have enough CPU cores / runners to run jobs in parallel

Copy link
Collaborator Author

@saienduri saienduri Aug 21, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah mi250 is a bit slower than w7900. Not sure how the mi300 fares, but it was initially why I picked w7900. Specifically the w7900 has an AMD Ryzen Threadripper PRO 7975WX 32-Cores while the mi 250 has an AMD EPYC 7713 64-Core Processor. The mi300 has an AMD EPYC 9454 48-Core Processor, so I don't think that will be any better. We should get another CI machine up with just the threadripper CPU in the lab :)

backend: cpu
runs-on: nodai-amdgpu-w7900-x86-64
runs-on: persistent-cache
saienduri marked this conversation as resolved.
Show resolved Hide resolved

# AMD GPU
- name: amdgpu_rocm_mi250_gfx90a
Expand Down
Loading