Open Bug 899783 Opened 7 years ago Updated 7 years ago
D2D initialization delays first paint by hundreds of milliseconds
I was measuring startup times for bug 890336, and I noticed that D2D initialization prolongs Nightly 25 startup time by almost 500ms. Cold startups are delayed by almost a full second. In particular, the time from creating the top level window to first paint is most affected. Startup times with D2D disabled (driver blacklisted): https://docs.google.com/spreadsheet/ccc?key=0Aq4ElA0owpEbdHE0S1BiUlBTVWZqeTYtajFfanJzX0E&usp=sharing Startup times with D2D force-enabled: https://docs.google.com/spreadsheet/ccc?key=0Aq4ElA0owpEbdG9sdVY5WXZVV3dHbm9jUU5aVktlTXc&usp=sharing Note: The "stock" build in the above documents is Nightly 25 from July 9th. The "patched" build is a modified version from bug 890336 and is not relevant to this bug. The test machine is Jeff Muizelaar's "aquaman" laptop: AMD C-50 processor dual-core @ 1GHz, 2GB RAM shared with Radeon HD 6250M video card, 64-bit Windows 7.
Have these numbers changed recently at all? Did D2D1.1 make a difference?
Here's a profile collected from a Windows 7 Tryserver Talos ts_paint run: http://tests.themasta.com/cleopatra/?report=8b9530a5fb2506a691913979423a297da3a9ee07 https://dl.dropboxusercontent.com/u/2901861/Screenshots/Bildschirmfoto%202013-08-12%20um%2011.23.25.png
You need to log in before you can comment on or make changes to this bug.