Announcement
Collapse
No announcement yet.
Mesa RADV vs. AMDVLK Radeon Vulkan Performance For July 2021
Collapse
X
-
Originally posted by jrch2k8 View Posti meant clearly FOSS AMDVLK
Originally posted by jrch2k8 View PostAlso purely speaking about Vulkan i think RADV has way bigger userbase than closed AMDVLK since Vulkan hasn't been adapted too widely on enterprise software yet.Last edited by pal666; 26 July 2021, 05:54 PM.
Comment
-
-
Originally posted by pal666 View Postit's important. just when you pay for 1% of sales, you can expect 1% of developer time
not all, not even deserved 99%, but most of it
One driver that does the job right.
Currently AMD situation on Linux is a mess.
On NV you get CUDA,Optix, RT, DLSS goodness in one big good package. They even contribute to Proton to make DLSS Windows titles to work.
While on AMD; you need prop package for OpenCL to work, you need prop package to have RT but prop package has disastrous OpenGL portion compared to RadeonSI and vkd3d workloads doesn't work properly on it, while it does on RADV.
To me it seems like BS excuses from AMD, Nvidia does what AMD can't just fine.
Comment
-
Originally posted by Leopard View Post
Nvidia does the opposite then. Kudos to Nvidia.
One driver that does the job right.
Currently AMD situation on Linux is a mess.
On NV you get CUDA,Optix, RT, DLSS goodness in one big good package. They even contribute to Proton to make DLSS Windows titles to work.
While on AMD; you need prop package for OpenCL to work, you need prop package to have RT but prop package has disastrous OpenGL portion compared to RadeonSI and vkd3d workloads doesn't work properly on it, while it does on RADV.
To me it seems like BS excuses from AMD, Nvidia does what AMD can't just fine.- Xorg doesn't use 100% CPU when rendering two applications at once
- KDE notifications don't stall the render pipe line and cause dropped frames across the board
- Multiple displays don't cause screen tearing on mixed refresh rate (Using TearFree in xorg.conf)
- GPU acceleration in firefox doesn't cause other windows to render at less than 30fps
- Displays are detected properly and limited RGB and interlaced modes are ignored (yes, nvidia loves randomly picking limited rgb and interlaced modes when available)
- Video acceleration is available using VA-API in Chromium + Firefox
- Wayland
If you're all for checking boxes on a spreadsheet, buy nvidia. If you actually use your system and want to not pull your hair out, use AMD.
- Likes 1
Comment
-
Originally posted by damentz View Post
No, Nvidia is much worse. I just recently switched from a 980 TI to a 6700xt and here's the list of upgrades (besides just overall being faster):- Xorg doesn't use 100% CPU when rendering two applications at once
- KDE notifications don't stall the render pipe line and cause dropped frames across the board
- Multiple displays don't cause screen tearing on mixed refresh rate (Using TearFree in xorg.conf)
- GPU acceleration in firefox doesn't cause other windows to render at less than 30fps
- Displays are detected properly and limited RGB and interlaced modes are ignored (yes, nvidia loves randomly picking limited rgb and interlaced modes when available)
- Video acceleration is available using VA-API in Chromium + Firefox
- Wayland
If you're all for checking boxes on a spreadsheet, buy nvidia. If you actually use your system and want to not pull your hair out, use AMD.
I won't argue with missing HW video acceleration - but this is a general Linux issue, not NVIDIA's, and I don't use Wayland, not intend to in the next five years. I like feature-complete projects.
Comment
Comment