What's happening with the VP8 libvpx benchmark on AMD?
There's a bunch of compute-bound-in-userspace ones (compiling, C-Ray, ffmpeg, x264) where the kernel doesn't matter at all, and that's unsurprising. But starting off that group of tests, there's the VP8 encoding one, where on AMD hardware .. WTF? A factor of two?
Almost exactly two, as though the application mis-guessed how many threads or processes to spawn. But only that one app on that one kernel with that particular hardware. Bug?
There's a bunch of compute-bound-in-userspace ones (compiling, C-Ray, ffmpeg, x264) where the kernel doesn't matter at all, and that's unsurprising. But starting off that group of tests, there's the VP8 encoding one, where on AMD hardware .. WTF? A factor of two?
Almost exactly two, as though the application mis-guessed how many threads or processes to spawn. But only that one app on that one kernel with that particular hardware. Bug?
Comment