Human benchmark test how to#
Human benchmark test 1080p#
Human benchmark test .exe#

Mine seems to vary by a significant margin. What is impressive about your clicks are the consistency. Since I've been on a mouse conquest its been interesting playing with HBM website. I've been interested in this due to how my machine handles USB and reading that mouse should always go to the ports the CPU vs the ports the chipset. Be sure to use at least 5 clicks sample size.

I'm curious to see some results as well as the web one. I wonder if it's possible to do something about this, perhaps writing the program in driver mode? O_o It is my understanding that at least some of the CPU overhead in calling Present() is due to the context switch of windows having to go driver side in kernel mode. Since I don't, the only metric I have to judge by is FPS numbers, and I know if my implementation ends up producing more FPS it should generally perform better as well. However I do not myself have an Arduino/Teensy yet to test this myself and the numbers are from somebody else who does. I suspect there could be a power saving issue in the graphic card, probably not in the CPU as the CPU should remain active due to busy input listening. Not producing frames at all and simply waiting for the input before calling Present() - This does make sense and I have tried that, but empirically the best-case results were somehow worse. Almost all of the run time is being spent in the Present() call which is out of my control. I've implemented an option to use a separate thread for input and rendering, but the results are about the same. Different graphical implementation which one?

Human benchmark test 1080p#

I rather like 1080p and feel as though deviating from that makes the task more synthetic and less applicable to real world situations. Lowering resolution and or color space.

Human benchmark test how to#

If anyone has ideas on how to get an increase in speed I would love to hear them. My focus was on getting everything to run as fast as I can. Once I've had the program going, implementing the human benchmark from it was trivial, and since I figured people might be interested in it I am sharing it here. With lower resolutions it goes up to 16k FPS or so. Quite interesting since I have a very strong CPU (i9-9900k) and relatively weak graphic card (GTX 960). My graphic card is showing 82% and I am CPU bound. The program runs at ~6.7k-6.9k FPS on my machine producing full color, full screen resolution frames of a single color. DirectX9 ended up giving me the best performance so that's what I went with. I've first implemented it in Love2D, then when I wasn't happy with the performance I've implemented it in DirectX9, DirectX12, OpenGL, and Vulkan to see which one is faster. My original goal was to implement a program that changes the color of the screen on a keypress. Needless to say it is much faster than the web version. It keeps stats of min/max/avg delay as well as how many early clicks you had. First click turns screen red, after a random 3-4 seconds delay turns screen green similar to the popular Human Benchmark website. Esc to quit.ī - Uses mouse buttons (and Esc to quit).

Human benchmark test .exe#

exe - changes screen color to white when pressing 'w' button, changes to black when pressing 'b'.