Real-world workload
CPU profile
Filtered self time
Largest virtual DOM hotspots
Unrelated functions are excluded
Sampled stacks
Virtual DOM functions
Self and inclusive CPU time
| Function | Self | Inclusive | Samples | Contexts |
|---|
End-to-end duration
Slowest tests
Top 50 sequential tests
| Test | Status | Duration |
|---|
Execution contexts
Page and worker profiles
Browser-wide V8 sampling
| Context | Total sampled | Virtual DOM inclusive | Samples |
|---|
Methodology
What is included
The Chrome DevTools Protocol records one continuous V8 CPU profile for
the page and every worker while /tests/_all.html runs the
suite without reloading the page between tests. By default, this is
repeated in five fresh browser profiles. The analysis attributes each
sample to its leaf function, reconstructs parent stacks for inclusive
time, and keeps functions whose source URL or function name belongs to
the virtual DOM implementation. Native browser work such as
document.createElement can contribute to a virtual DOM
caller's inclusive time, but is intentionally absent from the filtered
JavaScript hotspot list.