[Webkit-unassigned] [Bug 88446] New: Web Inspector: profiler - differentiate between native code (program) and idle time
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jun 6 13:08:00 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=88446
Summary: Web Inspector: profiler - differentiate between native
code (program) and idle time
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: paul.irish at gmail.com
CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
pmuellr at yahoo.com, joepeck at webkit.org,
pfeldman at chromium.org, yurys at chromium.org,
bweinstein at apple.com, apavlov at chromium.org,
loislo at chromium.org
The term (program) in the profiler is unclear to developers. It accounts for native code execution (captured by about:profiler in chromium) as well as idle time. Is it possible to identify what is real idle time?
A common use case is:
* User starts recording a profiler session
* User does an action which could use optimization
* User stops recording
What often happens is that the added time to manually start/stop the profiler in the GUI adds so much idle time that (program) can have %s of 90% or more. This makes the remaining percentages quite small and the user has to find "very expensive" operations that are taking < 1%.
"(idle)" would would help clarify this situation as well as perhaps an ability to filter out Idle time from the profiling totals.
>From mnaganov:
> Idle time is still native code time, so they both are combined in (program). To distinguish between them, we could tell the profiler that certain native functions it sees on the call stack actually mean idleness.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list