Skip to content
0:00 / 0:00

#windows7#gdi#wddm

Windows 7 GUI slowness

VooD

67 subscribers • 1 video on Hallway

YouTube
  • Recommended by 1 person: 1 on Hacker News.

Intermediate. Assumes working knowledge.

22K views17 years ago1 recommendation

Systems programmingGraphics and audioOperating systemsPerformance and optimizationRendering

A demonstration of the 2D rendering performance differences between Windows XP and Windows 7 due to changes in GDI hardware acceleration.

This video demonstrates the slowness of the new Windows 7 GUI. Windows Display Drivers Model used in both Vista and 7 doesn't include the neccesary hardware accelerated 2D functions to make the graphics generated by GDI and GDI+ as fast as in Windows XP. Microsoft chose software render because they found too difficult to combine the new graphical engine with the old one. If you want to learn more about it read this: blogs.msdn.com/directx/archive/2009/05/12/2d-drawing-apis-in… GDI has dozens of functions: msdn.microsoft.com/en-us/library/dd145203%28VS.85%29.aspx GDI hardware acceleration in Windows 7 using WDDM 1.1 drivers has only these functions hardware accelerated: msdn.microsoft.com/en-us/library/dd434692.aspx WDDM 1.1 drivers makes mandatory this new "partial" GDI hardware acceleration. So any driver which claims to be 1.1 is already accelerating as much as it ever will. Too bad, the results I got were based on WDDM 1.1 drivers (both from nvidia and Microsoft itself). The video shows how slow is the services.msc window, and the graphical artifacts it has, but it's not the only one. The file explorer scrolling is also much slower than in XP. ( youtube.com/watch?v=ToFgYylqP_U ) The example in the video is probably one of the applications where this problem is more easily spotted but there are many others which show the same behavior in a different degrees depending on how they call GDI functions. Windows 7 has several integrated solutions to circumvent the lack of 2d graphical acceleration...the problem is those solutions require full rewrite of the every single application's gui in order to use the new direct2d and directwrite, including the ones bundled with the os (file explorer, dialog boxes, management windows, etc...) and that's not going to happen in years, not from Microsoft itself, nor from 3rd party developers. I don't see Adobe porting their suite to Direct2D any soon..and anyway, the system will always stay GDI/GDI+ based. I think they probably won't start gui rewriting until the next major Windows version is released.. Meanwhile we will not see any better results in this area over the time other than the ones related with the improvement in cpu speeds. So this is all we get. Microsoft had to include this partial GDI acceleration, because those functions were way too slow in software mode, but it seems they thought the rest of them were not.....(which is not correct). About the real world impact. I can clearly see the real world impact of this decision as soon as I boot Windows 7 and start working, but there is people who's not able to see the difference between a game running at 60 fps from the same game running a 30 fps or earing the difference between a 128kb mp3 and a real CD Audio. I guess all depends on how fast you are used to work with your computer, and wether Vista already seemed slow or not for you. All I can say is, there is a real diff

Why it's here

1 person recommends this, 1 disputes it

What people say. Engineers point to this video to demonstrate how Windows UI responsiveness declined after Windows XP due to changes in the driver model.

kasabalion Hacker News • Recommends

On “Kill DWM (on Windows11) for less input lag and better performance”

Here's a more honest and direct introduction than Microsoft itself could wrote: link Especially follow the YouTube links demonstrating the problem: link to this video link

testz3453on Hacker News • Disputes

On “Ten years of Windows XP: how longevity became a curse”

I will use Windows XP for another 5 years - until new software and hardware will stop working on XP. Windows 7 GUI is 5 times slower than XP and has bugs: link to this video (Windows 7 GUI slowness) link (Windows 7 GUI slowness: file explorer) Windows 7 uses 5 times as much resources: XP: 233MHz, 64MB RAM, 1.5 GB. 7: 1GHz, 1GB RAM, 16 GB.

createaccount0on Hacker News • Mentions

On “Windows 8.1 now available”

I tried it on a new computer (Haswell desktop with SSD). But Windows 8.1 is still slower than XP. Even though I disabled all animations I can feel some lag between clicks and response. Probably it's because of this: link to this video ("Windows 7 GUI slowness") I'm going back to XP, but I needed to buy a dedicated graphics card because Intel HD doesn't have drivers for XP. And there's also 3GB RAM limit.

StillBoredon Hacker News • Mentions

On “24-core CPU and I can’t move my mouse”

Actually, its not as accelerated as it was back in the winXP days. Here is a random link about it: link to this video . Basically, the GPU card vendors could hook any part of the win32 GDI pre windows vista, and they did. Post vista, only a tiny portion of the GDI is accelerated. In theory you can avoid this by writing your application using a more modern API, but the vast majority of native windows applications continue to basically be GDI based due to age, or various GUI toolkits still being GDI based. Worse there are a number of toolkits (or browsers) which implement their own drawing routines rather than calling the system supplied ones. The final composited results with aero are of course accelera…

StillBoredon Hacker News • Mentions

On “MaXX Interactive Desktop: A Re-Implementation of the IRIX Interactive Desktop”

…to its responsiveness. But even then pre-vista much of the win32 GDI/drawing API was basically implemented in hardware on the GPU. If you get an old 2d win32 API benchmark, you will notice that modern machines don't tend to fare well in raw API call performance. 30 seconds poking around on youtube, should find you a bunch of comparisons like this link to this video . Keep in mind that even in 2020 pretty much every application on the machine is still relying on GDI (same as linux apps relying on xlib). Input+processing lag, USB is polling with a fairly slow poll interval rate (think a hundred or so ms). Combined with the fact that the keystrokes/events then end up queued/scheduled through multiple sub…

ndiddyon Hacker News • Mentions

On “Windows 10 refuses to go gentle into that good night”

I remember when 7 came out and people complained about how the UI was less responsive than XP! Example: link to this video I guess Windows UI responsiveness has just been steadily declining since the early 2000s.