Skip to content
Branch: master
Find file Copy path
Find file Copy path
1 contributor

Users who have contributed to this file

141 lines (102 sloc) 7.21 KB


New React profiling component that collects timing information in order to measure the "cost" of rendering.

This component will also integrate with the experimental interaction-tracking API so that tracked interactions can be correlated with the render(s) they cause. This enables the calculation of "wall time" (elapsed real time) from when e.g. a user clicks a form button until when the DOM is updated in response. It also enables long-running renders to be more easily attributed and reproduced.

Note that an experimental release of the Profiler component was first included with version 16.4 as React.unstable_Profiler. It did not yet support interaction tracing as that package had not been released.

Usage example

Profiler can be declared anywhere within a React tree to measure the cost of rendering that portion of the tree.

For example, to profile a Navigation component and its descendants:

    <Profiler id="Navigation" onRender={callback}>
      <Navigation {...props} />
    <Main {...props} />

Multiple Profiler components can be used to measure different parts of an application:

    <Profiler id="Navigation" onRender={callback}>
      <Navigation {...props} />
    <Profiler id="Main" onRender={callback}>
      <Main {...props} />

Profiler components can also be nested to measure different components within the same subtree:

    <Profiler id="Panel" onRender={callback}>
      <Panel {...props}>
        <Profiler id="Content" onRender={callback}>
          <Content {...props} />
        <Profiler id="PreviewPane" onRender={callback}>
          <PreviewPane {...props} />

Although Profiler is a light-weight component, it should be used only when necessary; each use adds some CPU and memory overhead to an application.


It is important for render timing metrics to work properly with React's experimental concurrent rendering mode. In concurrent mode, React may yield to the browser periodically so that an app remains responsive even on low-powered devices. This yielded time (when React is not running) should not be included when considering the "cost" of a render. This distinction is not possible to implement in user space.

Timing measurements should also be significantly lighter weight than the current User Timing API so that they can be gathered in production without negatively impacting user experience. (The User Timing API is currently disabled for production because it is slow.) In addition to a faster implementation, we can further limit the impact on existing apps by creating a new production + profiling bundle. This way, apps that don't make use of the Profiler component (or wish to disable it globally) will not incur any additional overhead. (The Profiler component will render its children in production mode but its onRender callback will not be called.)

Detailed design

The onRender callback is called each time a component within the Profiler renders. It receives the following parameters:

function onRenderCallback(
  id: string,
  phase: "mount" | "update",
  actualDuration: number,
  baseDuration: number,
  startTime: number,
  commitTime: number,
  interactions: Set<{ name: string, timestamp: number }>,
): void {
  // Aggregate or log render timings...

id: string

The id value of the Profiler tag that was measured. This value can change between renders if e.g. it is derived from state or props.

phase: "mount" | "update"

Identifies whether this component has just been mounted or re-rendered due to a change in state or props.

actualDuration: number

Time spent rendering the Profiler and its descendants for the current (most recent recent) update. This time tells us how well the subtree makes use of memoization (e.g. React.memo, useMemo, shouldComponentUpdate).

Ideally, this time should decrease significantly after the initial mount as many of the descendants will only need to re-render if their specific props change.

Note that in async mode, under certain conditions, React might render the same component more than once as part of a single commit. (In this event, the "actual" time for an update might be larger than the initial time.)

baseDuration: number

Duration of the most recent render time for each individual component within the Profiler tree. In other words, this value will only change when a component is re-rendered. It reflects a worst-case cost of rendering (e.g. the initial mount or a tree with no memoization).

startTime: number

Start time identifies when a particular commit started rendering. Although insufficient to determine the cause of the render, it can at least be used to rule out certain interactions (e.g. mouse click, Flux action). This may be helpful if you are also collecting other types of interactions and trying to correlate them with renders.

Start time isn't just the commit time less the "actual" time, because in async rendering mode React may yield during a render. This "yielded time" (when React was not doing work) is not included in either the "actual" or "base" time measurements.

commitTime: number

Commit time could be roughly determined using e.g. within the onRender callback, but multiple Profiler components would end up with slightly different times for a single commit. Instead, an explicit time is provided (shared between all Profilers in the commit) enabling them to be grouped if desirable.

interactions: Set<{ name: string, timestamp: number }>

Set of interactions that were being tracked (via the interaction-tracking package) when this commit was initially scheduled (e.g. when render or setState were called).

In the event of a cascading render (e.g. an update scheduled from an effect or componentDidMount/componentDidUpdate) React will forward these interactions along to the subsequent onRender calls.


Overuse of this component might negatively impact application performance.


None considered.

Adoption strategy

This is an entirely new component. Adoption can be organic and gradual.

How we teach this

A blog post would be a good initial start.

Perhaps we could provide some sort of discoverability within React DevTools.

Related proposals

Related documentation

You can’t perform that action at this time.