v153 · self-profiling markers
Profile something, for real
A real Profiler, a real workload, and the trace it produced. Nothing here is a mock-up: the sample count, the stacks, the frame names and the resource list are all read out of the object the browser handed back.
Choose something to profile
The sample interval requested is 10ms, and the browser is free to give you something coarser. Compare the sample count against the elapsed time to see what you actually got — a 300ms run at a true 10ms interval would be about 30 samples.
Where the samples landed
This is self time by leaf frame: for each sample, the function at the top of its stack. It is the simplest useful reading of a self-profile, and it is also where the missing samples hurt — a frame's share is a share of the samples that had a stack at all.
The trace, as the browser returned it
| # | timestamp | stackId | marker | leaf frame |
|---|---|---|---|---|
| Not run yet. | ||||