Hello,
The timeline and flame graph features of Chrome's DevTools have been very useful for us as we work to understand and improve the performance of VisualEditor. Someone asked me today about how we use these tools, so I recorded a short (3-minute) screencast. It unfortunately cut off near the end, but only the last sentence or so got clipped.
https://commons.wikimedia.org/wiki/File:Demonstration_of_Chromium%27s_timeli...
T88590 is a good example of a bug we caught using this feature:
https://phabricator.wikimedia.org/T88590
Hope it's useful,
Ori
Thanks, Ori!
Another great tool that we have been using heavily for JS profiling is https://github.com/jlfwong/chrome2calltree. It allows you to use the excellent KCachegrind profile viewer, which has call graphs, relative call frequency, grouping by file & other useful features. It works with profiles generated by V8, including Chrome.
It also powers https://github.com/gwicke/nodegrind tool, which makes it really easy to profile node projects by just calling 'nodegrind script.js' instead of 'node script.js'.
Gabriel
On Fri, Feb 13, 2015 at 4:56 PM, Ori Livneh ori@wikimedia.org wrote:
Hello,
The timeline and flame graph features of Chrome's DevTools have been very useful for us as we work to understand and improve the performance of VisualEditor. Someone asked me today about how we use these tools, so I recorded a short (3-minute) screencast. It unfortunately cut off near the end, but only the last sentence or so got clipped.
https://commons.wikimedia.org/wiki/File:Demonstration_of_Chromium%27s_timeli...
T88590 is a good example of a bug we caught using this feature:
https://phabricator.wikimedia.org/T88590
Hope it's useful,
Ori
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering
PS: added these links to our growing collection of JS optimization tips at https://www.mediawiki.org/wiki/Learning_JavaScript#Profiling.
On Fri, Feb 13, 2015 at 5:15 PM, Gabriel Wicke gwicke@wikimedia.org wrote:
Thanks, Ori!
Another great tool that we have been using heavily for JS profiling is https://github.com/jlfwong/chrome2calltree. It allows you to use the excellent KCachegrind profile viewer, which has call graphs, relative call frequency, grouping by file & other useful features. It works with profiles generated by V8, including Chrome.
It also powers https://github.com/gwicke/nodegrind tool, which makes it really easy to profile node projects by just calling 'nodegrind script.js' instead of 'node script.js'.
Gabriel
On Fri, Feb 13, 2015 at 4:56 PM, Ori Livneh ori@wikimedia.org wrote:
Hello,
The timeline and flame graph features of Chrome's DevTools have been very useful for us as we work to understand and improve the performance of VisualEditor. Someone asked me today about how we use these tools, so I recorded a short (3-minute) screencast. It unfortunately cut off near the end, but only the last sentence or so got clipped.
https://commons.wikimedia.org/wiki/File:Demonstration_of_Chromium%27s_timeli...
T88590 is a good example of a bug we caught using this feature:
https://phabricator.wikimedia.org/T88590
Hope it's useful,
Ori
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering
wikitech-l@lists.wikimedia.org