Skip to content

Explicit Gemm Search Limitation#5299

Open
cderb wants to merge 14 commits intodevelopfrom
users/cderb/explicit_gemm_limits
Open

Explicit Gemm Search Limitation#5299
cderb wants to merge 14 commits intodevelopfrom
users/cderb/explicit_gemm_limits

Conversation

@cderb
Copy link
Contributor

@cderb cderb commented Mar 10, 2026

Motivation

Explicit gemm solvers are on some occasions 500 - 1000s of times slower than the winning solver. We would like to prevent the testing of these mal-performant gemms such that tuning time is not needlessly lengthened

Technical Details

This change add function IsSlow to the gemm solvers to return if the gemm is predicted to have poor performance for the current convolution. And will be skipped if the function returns true.

Test Plan

Rules tested against collected tuning data. The rule sets are scored by selection metrics taking into account True Positives and False Positives as a percentage of the sampled convolutions where each solver was applicable.

Test Result

MI355 FPR TPR
FWD 9.02 88.22
BWD 9.27 92.93
WRW 5.56 72.75
NAVI FPR TPR
FWD 5.05 86.23
BWD 13.80 90.20
WRW 8.01 87.91

Jira ticket:
https://amd-hub.atlassian.net/browse/ALMIOPEN-807

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants