Repository navigation
Replies: 2 comments
|
One thing stands out in the patch script: the workgroup change assigns I'd test the Could you share the resulting C++ diff and base commit? The final diff would be easier to review than the replacement script. For validation, I'd compare baseline, selector-only and full-patch builds using repeated identical benchmarks, then check numerical correctness for the affected operations. Also, the condition covers AMD RDNA3 UMA devices generally, not just the 780M. |
|
Thank you @Miko997 for taking the time to look at this! I think you're right about how you narrowed it down! As for the baseline, when I tried the patch I believe it was on this commit: f172be7 So that would be base commit: 4da6337 I've also made them into diff/patch files, you're right that's a lot easier, let me know if this wasn't what you meant as I'm not completely sure: rdna3_mmvq_selector_only.patch rdna3_narrow_mmvq.patch (this was the full original patch) Benchmarks Baseline: rdna3_mmvq_selector_only.patch rdna3_narrow_mmvq.patch |
Uh oh!
There was an error while loading. Please reload this page.
Hi guys,
Disclaimer: I'm kind of in over my head with this and used AI for the patch, but figured it may be worth mentioning.
I was reading this comment from @reuvenneumann here:
#20831 (comment)
So I got curious and looked into whether the same applied to the Vulkan backend, and wrote a small patch which gave me a +12.2% increase in tg speed. I'm wondering if this is something that's already known or worth looking into more? I just did a quick speed test with the same prompt, nothing more.
gemma-4-26B-A4B-it-QAT-Q4_0.ggufPatch:
Thank you for your time.
All reactions