You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Vulkan with RX6800 (Windows driver), x axis is the tile size:
Similar results with a RX 5700XT.
According to my tests, the optimal tile size for VAE decoding on Vulkan backend seems to be 26. But I'm really confused about the huge drop of performance that happens for tile sizes between 10 and 25 for no obvious reason. I'm not noticing the same thing on CPU so far (CPU performance seems pretty consistent, with a very slight performance adventage for smaller tile sizes that should not matter in practice)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
On Vulkan with RX6800 (Windows driver), x axis is the tile size:
Similar results with a RX 5700XT.
According to my tests, the optimal tile size for VAE decoding on Vulkan backend seems to be 26. But I'm really confused about the huge drop of performance that happens for tile sizes between 10 and 25 for no obvious reason. I'm not noticing the same thing on CPU so far (CPU performance seems pretty consistent, with a very slight performance adventage for smaller tile sizes that should not matter in practice)
Beta Was this translation helpful? Give feedback.
All reactions