mirror of
https://github.com/Comfy-Org/comfy-kitchen.git
synced 2026-11-04 23:37:42 +00:00
[GH-ISSUE #68] INT8 matmul autotune uses NVIDIA-tuned configs on AMD RDNA #23
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/comfy-kitchen#23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @liminfei-amd on GitHub (Jul 10, 2026).
Original GitHub issue: https://github.com/Comfy-Org/comfy-kitchen/issues/68
The two INT8 matmul Triton kernels ship 6 autotune configs tuned for NVIDIA
(
num_stages=3–4,block_n=256). On AMD RDNA these are suboptimal — RDNA prefers shallowsoftware pipelining (
num_stages=2) and deeperblock_k.A
triton.testing.do_benchsweep on gfx1100 (RDNA3) and gfx1201 (RDNA4) shows an RDNA-tunednum_stages=2pool is ~1.03–1.11× faster per shape across typical DiT/SD INT8 GEMM shapes.Proposal: add
_int8_autotune_configs()that returns an RDNA pool whentorch.version.hipis set, keeping the NVIDIA list unchanged for CUDA. INT8 GEMM is int32-exact, so this changes
speed only (outputs byte-identical). PR ready.
@Ph0rk0z commented on GitHub (Jul 13, 2026):
The configs for turning weren't optimal either. I end up adding them myself.