2 ms·
OK... but let's say I'm a professional. That's a big sell. Having dedicated HW to do something faster than CPU is a bonus, not cheating.
by gjsman-1000 6y ago
OK... but let's say I'm a professional. That's a big sell. Having dedicated HW to do something faster than CPU is a bonus, not cheating.
- majewsky 6y agoWell yeah, for that one use case. But you cannot go from "X is 20% faster than Y at H265" to "X is 20% faster than Y at doing computer stuff".
- joefourier 6y agoYou already have HW encoder blocks on certain CPUs and most GPUs. See: Intel Quicksync, Nvidia NVENC and AMD Video Core Next. Support for them will of course depend on your platform and the applications you are using. IIRC, video editing software will generally use HW decoding for smooth-real time playback, but use CPU-encoding for the final output.
- rkangel 6y agoAbsolutely. But how many of those hardware blocks exist for what you want to do? If you care about H265, great. Let's say you get a dozen specific hardware accelerators, that's still only 12 tasks. That might end up covering the vast majority of web browsing tasks (to pick one example), but particularly as an engineer there is always going to be something else. And not all intensive tasks are amenable to hardware acceleration, e.g. compilation. That's why we care about general purpose CPU performance - at some point you always need it. Incidentally, this is philosophically the idea behind processors with built in FPGA capability. The hardware acceleration would just be a binary blob that could be loaded in and used when necessary. It could be continually updated, and provided with whatever software needed it.
- AnthonyMouse 6y agoNot only that, what happens over time? Not long ago the hardware accelerated codec would have been H.264. Soon it could be AV1. We're already at the point that professionals could want to be using AV1.