about HWBOT benchmark

[elita]

During my tests for 2024 competition, saw that HPET has to be turned on. At first, I didn't think much of it, until I noticed that almost every program in win11$$ will be negatively affected by this.

What is worse, once I turned it on for the benchmark to work finally, I forgot, I had it still on and went nuts, trying to find the culprit slowing my computer down to -50%.

My second question is, why HWBOT uses such an ancient early alpha attempt on what will become FFmpeg in the future. The latest FFmpeg (7.1 or newer) has hardware accelerated video encoding for that exact thing, that this benchmark is having us do in extra long and slow on purpose.

What purpose does this satisfy?

The HW-acceleration is specifically programmed to make use of the on-die and what Intel call UHDxx0 graphics. Most desktop model have such a device on them, unless you buy an -F CPU, meaning -F in the end means no video on the CPU. This accelerator is called QSV for short and means Intel's Quicksync. Quicksync is very common these days, since it allows you to broadcast your encoded content in real-time to platforms like Twitch or the YouTube.

So for example that 4K benchmark would be done in a few seconds, with very high frame rates, and it doesn't slow your CPU down. You could render that video in 2-5x real-time and still play Cyberpunk if you like.

[Leeghoofd]

it depends on the benchmark and if you are referring to HWBOT X265 , it had a vulnerability with HPET off on specific sockets. 

So we had to impose HPET on and only allow version 2.3 to be used
 

This is the same for everybody and is the outcome of the exploit by other users

 

Just make a seperate bench OS