Blackmagic needs to get their head out of their butts with Davinci Resolve
Announcement
Collapse
No announcement yet.
Open-Source AMD Radeon Linux Graphics In Great Shape For Workstations, Handily Beating Proprietary Driver
Collapse
X
-
Michael
Really interesting benchmark & results, thanks for that!
Just one minor nitpick:
Maybe using the performance governor instead of ondemand would have pushed the open-source difference even further ahead of the proprietary competition because of the lower CPU overhead.
And since we are talking about workstation loads here, I assume a properly configured one should make use of the performance governor all the time.
(BTW, would be funny to know how many companies are spending more than 10k $ per workstation, only then to install an enterprise Linux distro with default settings & thus leaving alot of CPU power on the table...)
Comment
-
Originally posted by agd5f View PostThere are two separate teams. We still need to support other OSes so not having a closed source driver on Linux does not suddenly free up a lot of resources to work on Linux. Windows still needs a driver.
Yes Windows still needs a driver but that does not say that driver has to be 100 percent closed source. Yes this could possible reduce the number of teams. Or at least reduce duplication in effort.
Yes serous question currently not answers is the open source implementation only better under Linux or is it better everywhere. Of course to find out this mesa3d and other parts need to be taken to other platforms with drivers to access the gpu fully.
Yes it would be as interesting world if Intel and AMD was in fact sharing gpu driver development work on all platforms not just open source ones.
- Likes 4
Comment
-
Originally posted by brucethemoose View PostNeat. I wonder if AMD could eventually use some of the RadeonSI code in Windows?
At the risk of going off topic, I'd like to see some ROCM benchmarks from Phoronix if possible, ideally against an Nvidia RTX card running the proprietary drivers. PyTorch/TF performance will be a huge factor in my own buying decisions. The last time I had a AMD dGPU, I ragequit just trying to set rocm up, but it seems that the packaging has gotten *much* better now.
- Likes 1
Comment
-
Originally posted by HaikuUser01234 View Post2 teams, gotta ve honest, that's the dumbest fucking thing I've read in a while.
Just go to only open source and internally build only with the open source driver.
Comment
-
Originally posted by Mystro256 View Post
You've obviously never seen the mess that is Windows driver development. Sure Mesa would work on Windows, but there's piles of things that MS needs *cough*DRM*cough* that makes mesa pretty challenging to use. Although, Mesa is MIT I think, so they might be able to fork it and try to carry some non-free patches on a private tree, but it definitely doesn't come for free.
Imagine if even a quarter of the work put into the closed driver was instead put into Mesa.
Comment
-
Originally posted by bridgman View Post
In fairness, Marek put a lot of work into improving workstation app performance in the open source driver over the last couple of years. Without that I suspect AMDGPU-PRO might have been faster. Either way it's good to see.
Comment
-
Originally posted by agd5f View Post
There are two separate teams. We still need to support other OSes so not having a closed source driver on Linux does not suddenly free up a lot of resources to work on Linux. Windows still needs a driver.
Perhaps it is completely naive, but wouldn't it save ressources and bring more speed to the driver development, when you would do it with one driver oss code base, and work as a team on one driver then?
From the outside it may seem as a good idea, but of course I do not know your details and dependencies and management requierements and so on.
As a 6800 XT owner and Linux user, I would naturally be happy with as much quality and functionality in the oss driver such as good raytraycing for example.
Comment
Comment