Skip to content

[release/2.4][ROCm][TunableOp] Fix TunableOp warmup environment variable. (#147412)#2017

Merged
pruthvistony merged 1 commit intorelease/2.4from
release/2.4_fix_tunableop_warmup
Apr 21, 2025
Merged

[release/2.4][ROCm][TunableOp] Fix TunableOp warmup environment variable. (#147412)#2017
pruthvistony merged 1 commit intorelease/2.4from
release/2.4_fix_tunableop_warmup

Conversation

@naromero77amd
Copy link

This PR corrects the behavior of the TunableOp warmup variables:

PYTORCH_TUNABLEOP_MAX_WARMUP_DURATION_MS
PYTORCH_TUNABLEOP_MAX_WARMUP_ITERATIONS

See the updated comments which describe how the environment variables are intended to work. Previously, if you only set one of the two environment variables the warmup iters would always be zero.

Manually tested the four possible combinations to make sure things still behavior as intended.

Pull Request resolved: pytorch#147412
Approved by: https://github.com/jeffdaily

(cherry picked from commit 4b35139)

…#147412)

This PR corrects the behavior of the TunableOp warmup variables:
```
PYTORCH_TUNABLEOP_MAX_WARMUP_DURATION_MS
PYTORCH_TUNABLEOP_MAX_WARMUP_ITERATIONS
```

See the updated comments which describe how the environment variables are intended to work. Previously, if you only set one of the two environment variables the warmup iters would always be zero.

Manually tested the four possible combinations to make sure things still behavior as intended.

Pull Request resolved: pytorch#147412
Approved by: https://github.com/jeffdaily

(cherry picked from commit 4b35139)
@naromero77amd
Copy link
Author

naromero77amd commented Apr 3, 2025

This is a subtle bug that has been present for a while. I discovered it post PyTorch 2.6 release. Cherry picked from upstream and will need to be cherry picked into ROCm 2.5 and 2.6 release branches.

@naromero77amd naromero77amd changed the title [ROCm][TunableOp] Fix TunableOp warmup environment variable. (#147412) [release/2.4][ROCm][TunableOp] Fix TunableOp warmup environment variable. (#147412) Apr 3, 2025
@rocm-repo-management-api
Copy link

rocm-repo-management-api bot commented Apr 4, 2025

Jenkins build for a9992d4cd7685b64a1ca9c419925b6bcd19de1ef commit finished as SUCCESS
Links: Blue Ocean view / Build artifacts

@rocm-repo-management-api
Copy link

rocm-repo-management-api bot commented Apr 16, 2025

Jenkins build for a9992d4cd7685b64a1ca9c419925b6bcd19de1ef commit finished as FAILURE
Links: Blue Ocean view / Build artifacts

@pruthvistony pruthvistony merged commit 15f86de into release/2.4 Apr 21, 2025
5 of 7 checks passed
@pruthvistony pruthvistony deleted the release/2.4_fix_tunableop_warmup branch April 21, 2025 22:36
@naromero77amd
Copy link
Author

!cherry-pick --onto release/2.5

@naromero77amd naromero77amd restored the release/2.4_fix_tunableop_warmup branch April 21, 2025 22:46
rocm-mici pushed a commit that referenced this pull request Apr 21, 2025
…ble. (pytorch#147412) (#2017)

This PR corrects the behavior of the TunableOp warmup variables:
```
PYTORCH_TUNABLEOP_MAX_WARMUP_DURATION_MS
PYTORCH_TUNABLEOP_MAX_WARMUP_ITERATIONS
```

See the updated comments which describe how the environment variables
are intended to work. Previously, if you only set one of the two
environment variables the warmup iters would always be zero.

Manually tested the four possible combinations to make sure things still
behavior as intended.

Pull Request resolved: pytorch#147412
Approved by: https://github.com/jeffdaily

(cherry picked from commit 4b35139)
@rocm-mici
Copy link

Created branch autogenerated/release/2.5_cherry-pick_pr-2017 and #2040

@naromero77amd
Copy link
Author

!cherry-pick --onto release/2.6

@naromero77amd naromero77amd deleted the release/2.4_fix_tunableop_warmup branch April 21, 2025 23:29
rocm-mici pushed a commit that referenced this pull request Apr 21, 2025
…ble. (pytorch#147412) (#2017)

This PR corrects the behavior of the TunableOp warmup variables:
```
PYTORCH_TUNABLEOP_MAX_WARMUP_DURATION_MS
PYTORCH_TUNABLEOP_MAX_WARMUP_ITERATIONS
```

See the updated comments which describe how the environment variables
are intended to work. Previously, if you only set one of the two
environment variables the warmup iters would always be zero.

Manually tested the four possible combinations to make sure things still
behavior as intended.

Pull Request resolved: pytorch#147412
Approved by: https://github.com/jeffdaily

(cherry picked from commit 4b35139)
@rocm-mici
Copy link

Created branch autogenerated/release/2.6_cherry-pick_pr-2017 and #2042

jithunnair-amd pushed a commit that referenced this pull request Apr 22, 2025
…nvironment variable. (pytorch#147412) (#2040)

Cherry-pick of #2017

Co-authored-by: Nichols A. Romero <165712832+naromero77amd@users.noreply.github.com>
jithunnair-amd pushed a commit that referenced this pull request Apr 22, 2025
…nvironment variable. (pytorch#147412) (#2042)

Cherry-pick of #2017

Co-authored-by: Nichols A. Romero <165712832+naromero77amd@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants