Originally posted by devius
View Post
Announcement
Collapse
No announcement yet.
The Interesting Tale Of AMD's FirePro Drivers
Collapse
X
-
Michael Larabel
https://www.michaellarabel.com/
-
-
Originally posted by bug77 View PostI see four types of gray. That's more than halfway to a greyscale rainbow.
Regarding the drivers spiking 20% and then dropping in performance. My understanding from a programming perspective is that optimising code usually creates unmaintainable code. Verses code that is neat and easy to read, which can easily have new features added. It's an old conundrum to coding that goes way back. I think it's the reason why the wheel of compilers and languages keeps being reinvented. So the developers probably did include some speed improvements, which might have also made it more difficult to update the code, and so therefore regressed back to the older code. I could be wrong...
Comment
-
Originally posted by b15hop View PostMy understanding from a programming perspective is that optimising code usually creates unmaintainable code. Verses code that is neat and easy to read, which can easily have new features added. It's an old conundrum to coding that goes way back. I think it's the reason why the wheel of compilers and languages keeps being reinvented. So the developers probably did include some speed improvements, which might have also made it more difficult to update the code, and so therefore regressed back to the older code. I could be wrong...
Comment
-
Originally posted by deanjo View PostThat is the biggest crock of crap I have read. A talented and competent programmer can make optimized and readable code. Of course the person reading the code has to have at least the understanding of what the optimizations do for it to make sense.
Anyway, it's quite possible that marketing was pushing for something to show off, and time constraints caused a few issues.
It's also entirely possible for optimisations to have some unwanted side effects, and so had to be removed.
And you're quite correct - the person reading things has to understand what's going on. It's quite common for one person to know everything, and it makes complete sense to him/her, and for another person to look at it and not make heads or tales of things.
Comment
-
It very much looks like AMD spun there a bit. Or is it just coincidence that the performance spiked at the launches of the quarterly FireGL driver, and lowered back after that?
Alternatively, the quarterly driver comes from somewhat different branch than the monthlies, and anyone wanting performance should be running the quarterlies.
Comment
-
Originally posted by b15hop View PostYou're surprised that, there is so much grey? The website isn't much better. I'm sure the website could be improved a bit too for that matter heh. =)
Originally posted by b15hop View PostRegarding the drivers spiking 20% and then dropping in performance. My understanding from a programming perspective is that optimising code usually creates unmaintainable code. Verses code that is neat and easy to read, which can easily have new features added. It's an old conundrum to coding that goes way back. I think it's the reason why the wheel of compilers and languages keeps being reinvented. So the developers probably did include some speed improvements, which might have also made it more difficult to update the code, and so therefore regressed back to the older code. I could be wrong...
Comment
-
Originally posted by Michael View PostI've posted about this a couple times in other threads to readers wanting similar tables.... It's already implemented in the Phoronix Test Suite and OpenBenchmarking.org to auto-generate nicer tables. Here's an example of a completely auto-generated one right now:
PTS takes care of figuring out everything and coming up with a table to highlight the differences. Once Phoronix.com is using the OpenBenchmarking.org-embedded graphs rather than static PNG files (within a couple weeks hopefully), those tables will be included, but I am not bothering with any stopgap measures in the meantime or anything that requires more manual work on my part.
Anyway, in more constructive criticism: I think the simpler table posted earlier still looks way better than the PTS generated one. There's simply no need to have every version of the drivers have their own column, it makes it too wide to be useful. I assume that even if you took out the 1 row that changed (OpenGL version) it would still list them as separate columns? I see what you're trying to do here and the automated generation is neat but IMO it still needs some work.
Comment
-
Originally posted by smitty3268 View PostI assume that even if you took out the 1 row that changed (OpenGL version) it would still list them as separate columns? I see what you're trying to do here and the automated generation is neat but IMO it still needs some work.Michael Larabel
https://www.michaellarabel.com/
Comment
Comment