3 ms·
I would agree that our perf isn't the best. Almost all of that comes down to our rendering stack - something like 90% of our CPU time is spent rendering the win
by zadjii 8y ago
I would agree that our perf isn't the best. Almost all of that comes down to our rendering stack - something like 90% of our CPU time is spent rendering the window. This is because at the moment we're stuck with GDI, and IIRC we have to kernel-thunk every row of text we render. It's not a great situation.
Stay tuned for updates in this area though. Improving this experience is one of our top priorities.
- delfinom 8y agoGDI?! Throw that bad boy into the abandoned WPF framework and hardware accelerate it! (Without the sandbox shengigans of UWP in the way)
- bitcrazed 8y agoHi. Windows Console PM, and @zadjii's whipping boy here :) LOL :) Nice idea - though it turns out that this won't help. Don't ask me why we know this ;) We DO, however, (as @zadjii indicates above) have plans afoot to considerably improve Console's text rendering. Also note that scrolling speed is actually not a good measure of rendering perf! Why? Because at most, scrolling should max-out at around one vertical page every 1/60 of a second. Any more than that and the text tears. This may or may not be an issue for some, but tearing the text upsets people who're visually looking for a particular text layout-pattern which might get discarded if the Console scrolls faster than one page per refresh. This said, yes, we're gonna get faster with less CPU ;)