Comment #4 on issue 18361 by [email protected]: 10% slowdown in Mac startup tests http://code.google.com/p/chromium/issues/detail?id=18361
Agreed, but my point was what I checked in as a reference build throws a lot of messages on the floor, so we're not doing all the work we're supposed to do. With those messages now being honored, we're drawing more, sizing windows correctly (larger) (but still not honoring the testing framework sizing request), actually drawing when told instead of throwing the requests out and waiting for idle (which in most cases never comes in the tests). So I have no doubt there are things we can (and should) speed up, but we aren't very likely to maintain the exact same numbers, the added work will have some overhead. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
