Added limit on number of warps for coordesc autotuner

[Chillee]

Stack from ghstack (oldest at bottom):

• Add heuristic for when evict_first should be set (and some other minor things) #108841
• -> Added limit on number of warps for coordesc autotuner #108997

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @ngimel @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/108997

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• A100 runners down: apt-get install nvidia-docker2, Could not get lock /var/lib/dpkg/lock-frontend

✅ You can merge normally! (4 Unrelated Failures)

As of commit a2e3493 with merge base a6b153b ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• linux-focal-py3.11-clang10 / test (dynamo, 2, 2, linux.2xlarge) (gh)
• linux-focal-py3.8-clang10 / test (dynamo, 2, 2, linux.2xlarge) (gh)

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• linux-jammy-py3.9-clang12-asan / test (default, 2, 6, linux.4xlarge) (gh)

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

• cuda12.1-py3.10-gcc9-sm86 / test (inductor, 1, 1, linux.g5.4xlarge.nvidia.gpu, unstable) (gh)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[shunting314]

nit: 'CUDA has a maximum of 1024 threads' -> 'CUDA has a maximum of 1024 threads per block'?

[Chillee]

@pytorchbot merge -f "failures unrelated"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here