Chrome DevTools: JavaScript CPU Profiling in Chrome 57

In Chrome 57, which is currently Canary, the Timeline panel has been renamed to the Performance panel, the Profiles panel has been renamed to the Memory panel, and the Record JavaScript CPU Profile feature on the Profiles panel has been removed.

Have no fear, you can still profile your JavaScript from the Performance panel. In fact, that's why the Record JavaScript CPU Profile feature was removed. The workflows and layouts are a little different, but the Performance panel provides all of the same information as the old workflow, and then some.

This little migration guide shows you how to record a JS profile in the Performance panel, and how the Performance panel's UI maps to the old workflow that you're used to.

How to record a JS profile

  1. Open DevTools.
  2. Click the Performance tab.

    The Chrome DevTools Performance panel
    Figure 1. The Performance panel.

  3. Record in one of the following ways:

    • To profile a page load, click Record Page Load. DevTools automatically starts the recording and then automatically stops when it detects that the page has finished loading.
    • To profile a running page, click Record, perform the actions that you want to profile, and then click Stop when you're finished.

How the old workflow maps to the new

From the Chart view of the old workflow, the screenshot below shows you the position of the CPU usage overview chart (top arrow) and the flame chart (bottom arrow) in the new workflow.

Mapping between flame chart in old workflow and new workflow.
Figure 2. Mapping between flame chart in old workflow (left) and new workflow (right).

The Heavy (Bottom Up) view is available in the Bottom-Up tab:

Mapping betwen Bottom-Up view in old workflow and new workflow.
Figure 3. Mapping between Bottom-Up view in old workflow (left) and new workflow (right).

And the Tree (Top Down) view is available in the Call Tree tab:

Mapping betwen Tree view in old workflow and new workflow.
Figure 4. Mapping between Tree view in old workflow (left) and new workflow (right).

Feedback

How was this article? Great? Terrible? Let us know by answering the questions below.

Ping @ChromeDevTools on Twitter or open a GitHub issue on our docs repo if we missed any features, or if you have any other questions about this article.