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.

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

[Question] | How to generate config YAMLs for GridBased tensile tuning? #2033

Open
rtmadduri opened this issue Oct 15, 2024 · 2 comments
Open

Comments

@rtmadduri
Copy link

rtmadduri commented Oct 15, 2024

Hello Team,

We are trying to do Gridbased Tensile tuning for a project and we are following the instructions highlighted over here , however, it seems like the config generator only generate YAML files that correspond to Equality tuning. Are there special instructions to generate GridBased tuning YAML files?

Additionally, I went through a few config files mentioned in your repo. Can you help me understand what is the difference between Exact and Range? Is that the primary differentiator between Equality and Grid?

cc: @itej89, @feifei14119

@ppanchad-amd
Copy link

Hi @rtmadduri. Internal ticket has been created to assist with your issue. Thanks!

@zichguan-amd
Copy link

Hi @rtmadduri, Equality and GridBased are different searching methods for kernel selection. Equality is better because the library has the actual GEMM size kernel tuned, and if the library does not have the exact kernel size, it will fall back to GridBased and chose a kernel that is close to the GEMM size. The generated kernel YAML files is found based on this rule. The YAML files found in hipBLASLt are the ones that are tuned and used in the search process of Tensile.

Additionally, I went through a few config files mentioned in your repo. Can you help me understand what is the difference between Exact and Range? Is that the primary differentiator between Equality and Grid?

The difference between Exact and Range can be found here. Range specifies a range of sizes to benchmark while Exact specifies the exact size to benchmark.

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

No branches or pull requests

3 participants