3 ms·
They explicitly use Automatic1111 to demonstrate those speeds... Granted maybe not all extensions are compatible with DirectML in Automatic1111.
by FloatArtifact 3y ago
They explicitly use Automatic1111 to demonstrate those speeds...
Granted maybe not all extensions are compatible with DirectML in Automatic1111.
- roenxi 3y agoI do think the original comment was wrong (if they tested in Automatic1111 then ... enough said about it working). However, they still have a point in warning people about AMD cards. There is more risk to these things than Nvidia: - AMD's support is flaky. The AMD 7900 XTX is only officially supported on Windows PCs (for ROCm). On Linux PCs in my experience there is a high risk of graphics card hard lockups. - Historically AMD has dropped support for consumer cards really quickly (I don't think they support any consumer cards from more than about 3 years ago). At some point that'll stabilise, but it is hard to tell if this is the generation that will start working long term or the next. - AMD generally gets second class support in return from the machine learning communities. There still seems to be some chance that you'll be locked out of the latest and greatest if you go AMD. At some point this will all probably come good and it'll be like CPUs where there is really no difference between the vendors. There is too much interest in machine learning right now for anything else to happen ... but I've been buying AMD for more than a decade now and I've been thinking that for years already. If someone is on the edge they'd be better off not getting seduced by a minor performance improvement and sticking to Nvidia cards. It is uncertain when the long term will reach us. This year? 5 years? A decade? All options where AMDs software drivers are in play. Although AMDs graphics drivers do seem great on Linux nowadays, I like things that just work. It is a pity they got so out of position vs CUDA.
- nextaccountic 3y ago> On Linux PCs in my experience there is a high risk of graphics card hard lockups. What do you mean, does this become a crash / kernel panic? Is this a common occurrence and is it due to bad kernel drivers?
- paulmd 3y agoinfamously, geohot encountered and documented a bunch of these kernel panics. https://github.com/RadeonOpenCompute/ROCm/issues/2198 https://github.com/RadeonOpenCompute/ROCm/issues/2198 https://geohot.github.io/blog/jekyll/update/2023/06/07/a-dive-into-amds-drivers.html https://geohot.github.io/blog/jekyll/update/2023/06/07/a-div... they don't occur in amdgpu-pro proprietary userland, but AMD apparently runs that on an internal release cycle and doesn't make the current repo or build available to the public. And AMD just historically hasn't cared enough about the open userland to support that even in the officially-supported configurations. I'll also add to GP by saying that the windows support is all of about 2 weeks old at this point and it's also the first time that consumer cards (as opposed to the CDNA compute cards and the workstation-branded Radeon Pro cards) have had official support. Not that that is a guarantee it'll actually run with AMD though, especially on the open-source userland.
- roenxi 3y agoIt looks like a kernel panic to me, probably bad kernel drivers but I've never tried to figure out what is happening. My graphics card is more than 3 years old (ie, unsupported) so it isn't worth reporting.
- sassy_quat 3y ago[dead]