Originally posted by duby229
View Post
Announcement
Collapse
No announcement yet.
Intel Announces Early 8th Gen Core Processors, Coffee Lake
Collapse
X
-
No patches are needed, just install the appropriate drivers and compile with the appropriate flags, I do it all the time, choose here's my config for my current ffmpeg build:
--enable-nonfree --enable-gpl --enable-version3 --enable-libass --enable-libmp3lame --enable-libopus --enable-libfdk-aac --enable-libvpx --cpu=native --enable-vaapi --enable-vdpau --enable-libx264 --enable-libx265 --prefix=/apps/ffmpeg/git
You can also enable nvenc functionality by adding --enable-nvenc to the above parameters and enabling cuda is also failry simple.
If you need a compile guide, let me know.
Thanks.
Comment
-
Originally posted by duby229 View PostTroubleshooting what?
The trouble with that benchmark showed is it represents results -nobody- is going to see. Ever.
It's not showing how well the game runs, but how well the hardware runs vs the older hardware, since both ran the same test.
Comment
-
Originally posted by starshipeleven View PostFinding bottlenecks is troubleshooting.
It shows how the hardware has improved over time, which is what most synthetic benchmarks are for.
It's not showing how well the game runs, but how well the hardware runs vs the older hardware, since both ran the same test.Last edited by duby229; 25 September 2017, 01:01 PM.
Comment
-
Originally posted by duby229 View Post
It absolutely does not show improvement over time (or any bottlenecks at all). First of all you have to disable most of the games functionality and then reduce data to process by lowering resolution. (You have to increase data to process in order to hit most types of bottlenecks, not reduce them) It indicates a CPU's internal IO scalability with no provable facts at all. (And even then -only- when compared against real world settings on the same hardware) At best it -un-provably indicates- that AMD's architecture scales internal IO better than Intel's. Because games are so complex you cannot isolate what, why or how. You need specifically designed synthetics to do that. The best you can do is make un-provable inferences with it.
Looking forward to the 4k and 1080p results.Last edited by Sidicas; 25 September 2017, 01:49 PM.
- Likes 1
Comment
-
Originally posted by tomtomme View Post
4k is at least more relevant than 720p. Please show me a desktop system with a 720p screen nowadays. Many sites test at 720 to show the world something about the cpu that nobody will experience in their day to day work / game (besides laptop-gamers, but those are different cpus)
Comment
-
Originally posted by Sidicas View Post
Agreed. Been known in gaming communities for over a decade now that low resolution benchmarks are nothing more than RAM benchmarks. Where RAM performance is never a bottleneck in a gaming pc at normal and higher graphics settings.
Looking forward to the 4k and 1080p results.
Comment
-
Originally posted by Spooktra View PostNo patches are needed, just install the appropriate drivers and compile with the appropriate flags, I do it all the time, choose here's my config for my current ffmpeg build:
--enable-nonfree --enable-gpl --enable-version3 --enable-libass --enable-libmp3lame --enable-libopus --enable-libfdk-aac --enable-libvpx --cpu=native --enable-vaapi --enable-vdpau --enable-libx264 --enable-libx265 --prefix=/apps/ffmpeg/git
You can also enable nvenc functionality by adding --enable-nvenc to the above parameters and enabling cuda is also failry simple.
If you need a compile guide, let me know.
Thanks.
Comment
Comment