[Webkit-unassigned] [Bug 84889] Web Inspector: support flame graph visualization of CPU profiles

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=84889

Iraê <irae at irae.pro.br> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |irae at irae.pro.br

--- Comment #5 from Iraê <irae at irae.pro.br> ---
This is somewhat forgotten here, but other browsers already have this working. Chrome for quite a while and Firefox added recently. Looking at the timeline tab on WebInspector and the raw data from Chrome, looks like very similar, so WebKit might be able to port some code from Blink.

The Chrome team put up a very interesting, albeit a bit out dated, documentation about not only how to use the profiles tab on the browser but also how to interact with custom markers. Those marker were used by us on the Yahoo Search team and are super valuable in addition to regular browser events.

https://developer.chrome.com/devtools/docs/console#controlling-the-cpu-profiler

Also, Chrome advocates put up additional information in their own blogs and/or community websites like HTML5Rocks:

http://addyosmani.com/blog/devtools-flame-charts/
http://www.html5rocks.com/en/tutorials/developertools/novdigest/

Mozilla also have some interesting and slightly different approach. Those are largely the same tools, with different ways of rendering the same data:

https://developer.mozilla.org/en-US/docs/Tools/Performance/Flame_Chart

In closing, I would very much like to see this feature, specially for remote debugging actual iOS devices over USB. Different CPU architectures might yield different results, even if not that relevant, but having official support in webkit and eventually in Safari Mobile would be a huge improvement for mobile development. Specially since for many products iOS Mobile Safari has a huge percent of total daily active users.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150812/f64d1623/attachment.html>