Trace Model (NOT FOR PUBLIC CONSUMPTION)

This package contains the trace engine implementation used by the DevTools Performance Panel.

⚠️ The API is not stable and it's fairly likely that upgrades will break you (at some point). But the breakages should be obvious exceptions or type failures.

API quickstart

import * as TraceModel from '@paulirish/trace_engine';

polyfillDOMRect();
const engine = TraceModel.Processor.TraceProcessor.createWithAllHandlers();

await engine.parse(traceEvents);
console.log(engine.data) // TraceParseData

Note: To run in Node, you'll need to polyfill window.DOMRect. 😜

See the included analyze-trace.mjs a runnable invocation.

Types

You'll probably use something like…

@type {import('@paulirish/trace_engine').Types.TraceEvents.TraceEventData[]
@type {import('@paulirish/trace_engine').Handlers.Types.TraceParseData

Maintainer cheatsheet

See also http://go/btlax

# Build devtools and prep a package, then invoke the copy script to prepare $HOME/code/trace_engine
scripts/trace/prep-trace-engine-package.sh

# switch to standalone
cd $HOME/code/trace_engine

# bump and publish
npm version v0.0.XXX   # Manually determine next version. `npm info @paulirish/trace_engine | grep latest` + 1
npm publish --access public --dry-run
npm publish --access public

High level architecture

     ┌──────────────┐
     │  Model#parse ├───┐
     └──────────────┘   │
                        │
             ┌──────────▼──────────┐
             │async processor#parse│
             └──────────┬──────────┘
                        │
             ┌──────────▼────────────┐
             │for handler of handlers│
             └───┬────────────────┬──┘
                 │                │
┌────────────────▼────┐     ┌─────▼────────────────┐
│NetworkRequestHandler│     │...many more handlers │
│                     │     │                      │
│     reset()         │     │                      │
│                     │     │                      │
│     handleEvent()   │     │                      │
│                     │     │                      │
│     finalize()      │     │                      │
│                     │     │                      │
│     data()          │  │  │                      │
└─────────────────────┘  │  └──────────────────────┘
                         │
                         │
      ┌──────────────────▼─────────────────┐
      │const data = model.parsedTrace()│
      └────────────────────────────────────┘

Model#parse is the entrypoint into the engine and is the public interface that consumers use to initiate tracing and to fetch data back.

All the processing is done by the Processor. The processor contains a series of Handlers, each of which is responsible for parsing events of a particular category.

The trace processor loops over every event in the trace and calls each handler in turn (done this way so we only loop over the trace file once, rather than doing it once-per-handler). A Handler is a file that exposes a set of methods, most importantly handleEvent() and data(). The handleEvent function will be called for each event in the trace, and it is up to an individual handler to do something with that event if it needs to. The data method should return the final data that has been parsed and generated by the handler.

Once processing is done (read on for more details on how to track this), you can use the parsedTrace() method to fetch the result of parsing a given trace.

Enabled handlers and creating a model

We use Model.createWithAllHandlers(), which initializes a model configured correctly with the right handlers.

If you want to strictly control the set of handlers that are run (for example, if you only want to run one particular handler), you can initialize the model yourself and pass in the set of handlers:

const model = new Model({
  NetworkRequestHandler: Handlers.ModelHandlers.NetworkRequestHandler,
})

Parsing a trace and getting data back

Once you have an instance of the model, you can call the parse method to take a set of raw events and parse them. Once parsed, you then have to call the parsedTrace method, providing an index of the trace you want to have the data for. This is because any model can store a number of traces. Each trace is given an index, which starts at 0 and increments by one as a new trace is parsed.

If you are managing multiple traces, you should store them in some form of indexed data structure so you can easily know which index to use to fetch any data from the model. You may delete a trace with deleteTraceByIndex, which will then update the indexes of all other traces too.

If you need to check how many traces you have, you can call model.size(). The latest trace's index is therefore always model.size() - 1.

Waiting for updates from the model

When you call parse you have two options. You can await it, which will wait until the trace is fully parsed:

await this.model.parse();

But it's likely preferable to instead use events, to avoid blocking the UI whilst parsing is in progress. You can listen to the ModelUpdateEvent for updates:

this.model.addEventListener(Model.ModelUpdateEvent.eventName, event => {
  const {data} = event as Model.ModelUpdateEvent;

  if (data.data === 'done') {
    // trace is complete
    const newestData = this.model.parsedTrace(this.model.size() - 1);
  } else {
    // data.data will be an object: { index: X, total: Y}, which represents how many events (X) have been processed out of a total (Y).
    // This can be used to show a progress bar, for example.
  }
})

The structure of the final data object

The object returned from parsedTrace() is an object of key-value pairs where each key is the name of a handler, and the value is the data that was parsed and returned from that handler.

{
  NetworkRequestHandler: ReturnType<typeof NetworkRequestHandler['data']>,
  LayoutShiftHandler: ReturnType<typeof LayoutShiftHandler['data']>,
  // and so on for each enabled Handler
}