I'm not on the devtools team, but I'll take a swing at these. On Sun, Sep 20, 2009 at 1:12 AM, Andy <[email protected]> wrote: > The profiling feature looks very cool. I'm profiling some expensive > JavaScript, but most of the profile is attributed to "(program)" -- > 80-90%. What does this mean?
I believe that means that it's something in the renderer process other than javascript code. So it could be layout, image decoding, DOM manipulation, etc. > I don't see any documentation about the profiler (searching Google and > chromium.org, and even the source code). Is there any I'm missing? > It would be nice to know how the profiler works in general. It's still a work in progress, so no docs yet. The quick answer on how it works is that it's a sampling profiler. This means it doesn't account for 100% of code run (it may miss some very fast/short snippets of code), but that it's very lightweight, and does a pretty good job of identifying hotspots in your code. Erik > thanks, > Andy > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
