The hits keep on coming. I'm not sure whether to laugh or cry. https://nibblestew.blogspot.com/2021/07/looking-at-performance-of-refterm.html …
-
-
It's not GPU but I remembered this from a few years ago in VSCode. The blinking cursor was taking ~13% of CPU. Hilarious parallel that you can hopefully use to prove your opponents on this issue are not arguing in good faith. https://www.reddit.com/r/programming/comments/612v99/vs_code_uses_13_cpu_when_idle_due_to_blinking/ …https://developers.slashdot.org/story/17/03/24/1511252/blinking-cursor-devours-cpu-cycles-in-visual-studio-code-editor …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I would call myself absolutely unknowledgeable in the field of programming, but what the author described is beyond denial. I mean, his first sentence of what he believes what the sample code represents shows he even had read the first output the code draws on screen...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Waiting on an input handle as optimization would be an entire PhD project.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yeeah, that was a bit of a puzzler for me. "It runs at 1000s of FPS but uses 14% GPU!"... like, did the blogger not think that v-sync might help with that? And that the point of the proof of concept was to prove a concept and show how high the fps could be pushed? Mind-boggling.
-
It was pretty spectacular to watch somebody run a 7000fps demo and _not_ immediately understand that that would be 0% GPU usage for the exact same demo if you added a single call to MsgWaitForMultipleObjects.
End of conversation
New conversation -
-
-
But yo, don't you know the "code is arranged in a non-standard way?" - That has to account for at least 95% of the speed increase. Right? Right?!?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.