On Wed, Oct 28, 2009 at 12:24 PM, Antoine Labour <[email protected]> wrote: > On Wed, Oct 28, 2009 at 12:05 PM, Adam Barth <[email protected]> wrote: >> I bet the reason Windows startup feels slower is whatever drawing >> operation we're using for the main content area is slow. The >> top-to-bottom sweep probably makes me feel like the browser isn't >> loaded until the sweep reaches the bottom, whereas I feel like Linux >> is done earlier in its startup sequence. > > For the UI bits, I'm willing to believe that GTK, which uses cairo, hence > XRender for rendering, is hardware accelerated and in any case pipelined in > another process (X), and so is faster than serialized, software rendered > Skia. How much is the impact ? I don't know, we're not talking a huge amount > of pixels, but still...
I wonder if the problem is we're using a main-memory-to-video-memory blit to paint the content area in Windows on startup. How hard would it be to use a DDB during startup? That would give us a video-memory-to-video-memory blit, which can easily paint the whole screen at >180 fps. Adam --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
