On Mon, Aug 31, 2009 at 9:50 AM, Scott Hess <[email protected]> wrote: > It might be interesting to have the IO thread tag messages with the > time as they go by, and have the UI thread keep track of the > distribution of times that messages spend enqueued. Then we can set > goals around how fast IPCs get pulled off the queue.
Our debug builds have this info under: about:objects Which shows how long it took to service tasks posted to the various message loops. There is also some fancy URL notation to filter the results on that page, Jim could tell you more. On Mon, Aug 31, 2009 at 9:57 AM, John Abd-El-Malek <[email protected]> wrote: > > > On Mon, Aug 31, 2009 at 4:50 PM, Scott Hess <[email protected]> wrote: >> >> On Mon, Aug 31, 2009 at 8:56 AM, Mark Mentovai<[email protected]> wrote: >> > Well, that annoying throbber is still chewing up time, causing some >> > amount of UI loop contention while the images, thumbnails, and icons >> > are fetched. Windows and Linux don't have a throbber for the new tab >> > page. We shouldn't either. Excellent, now we're down to 200ms. It's >> > still high, but it's reasonable. It's a perceptible improvement from >> > the 300ms we started with. >> >> It might be interesting to have the IO thread tag messages with the >> time as they go by, and have the UI thread keep track of the >> distribution of times that messages spend enqueued. Then we can set >> goals around how fast IPCs get pulled off the queue. > > The IPC logging code already keeps track of message dispatch time (i.e. from > when Send() was called until the message handler started executing) and > processing time (i.e. how long the handler took). I don't know how much of > the UI is implemented on Mac, but on Windows this was only a few hours to > implement, and it'll give a lot of insight on which messages are backed > up/taking a lot of time. >> >> -scott >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
