Real-world workload
Renderer message benchmark
Virtual DOM calls received by renderer-process while the pinned Activity Bar, Explorer, About, and Title Bar end-to-end suites run.
Worker to frontend
Virtual DOM traffic by workload
Compact UTF-8 JSON bytes
| Workload | VDOM calls | Serialized size | All messages | Command bytes | Empty patches / duplicate CSS | Render intervals <16 ms | Captured data |
|---|
Protocol calls
Traffic by method
All direct and batched renderer commands
| Workload | Method | Calls | Serialized size |
|---|
Methodology
What the byte count means
The benchmark instruments the copied renderer-process bundle and
records only messages received from its dedicated Renderer Worker.
Chromium's DevTools Protocol returns a JSON-safe copy after
unsupported host objects such as MessagePort are removed.
The analysis extracts all direct and batched renderer commands, plus
the virtual DOM subset. It reports empty patch sets, repeated CSS, and
arrival intervals between render batches. Size is compact UTF-8 JSON,
a stable payload metric rather than an estimate of engine-specific
retained heap size.