bare vs Chrome: a measured baseline
One real end-to-end test on a staging web app, run in Chrome and in bare, on the same machine and the same minute. This is the baseline that later work is measured against.
IThe test
The app is a production Next.js and React dashboard for a voice-AI product, on its staging server. The test does what a QA engineer does by hand:
- Log in.
- Create a client.
- Create an agent for it with a three-step wizard: setup, name and voice, review.
- Delete the agent.
- Delete the client.
Both browsers run the same step file. bare runs it with bare-drive. Chrome runs it through a small driver over the DevTools protocol, the same protocol that Playwright uses. The Chrome driver sends real mouse events and waits until an element stops moving before it clicks. After every run, a script checks the app and finds no test data left behind.
IIMemory
Memory is the clearest result. bare is one process. Chrome starts 13 processes for one tab: the browser, a GPU process, renderers, utilities and crash handlers.
Headless runs, mean of 6 each. PSS splits shared pages between processes, so it is the fair total. RSS counts shared pages once per process, so it overstates Chrome.
IIITime and CPU
bare finishes the journey 1.25x faster and uses 1.3x less CPU time. Most of the CPU gap is in the kernel. Chrome spends 9x more kernel time on starting processes and passing messages between them.
Where bare is slower. bare runs 17% more user-space instructions than Chrome. This app is mostly React and app scripts. Chrome compiles JavaScript with V8. bare walks the syntax tree and has no JIT. On a small static test page in an earlier comparison, bare used 250x fewer instructions. On a script-heavy app, the JavaScript engine is the gap to close.
IVWhere the time goes
Each phase of the journey, mean of the headless runs. Most of each phase is network and server time, so both browsers are close. bare is faster in every phase.
VAll numbers
Mean of the runs, with the spread as (max − min) / mean in brackets. Ratio is Chrome ÷ bare: above 1 means Chrome uses more.
| Metric | Chrome | bare | Ratio |
|---|---|---|---|
| Journey time (s) | 8.26 (14%) | 6.63 (13%) | 1.25x |
| CPU total (s) | 5.12 (3%) | 3.95 (2%) | 1.30x |
| CPU user (s) | 4.23 | 3.85 | 1.10x |
| CPU kernel (s) | 0.89 | 0.10 | 9.3x |
| User instructions (G) | 25.4 (2%) | 29.7 (2%) | 0.86x |
| Peak PSS (MiB) | 429 (3%) | 84 (2%) | 5.1x |
| Peak RSS sum (MiB) | 1,217 | 87 | 14.1x |
| memory.peak (MiB) | 353 | 79 | 4.5x |
| Processes | 13 | 1 |
| Metric | Chrome | bare | Ratio |
|---|---|---|---|
| Journey time (s) | 7.96 (10%) | 6.84 (7%) | 1.16x |
| CPU total (s) | 5.51 (4%) | 4.45 (2%) | 1.24x |
| CPU user (s) | 4.30 | 4.36 | 0.99x |
| CPU kernel (s) | 1.21 | 0.10 | 12.6x |
| User instructions (G) | 28.0 (5%) | 34.5 (3%) | 0.81x |
| Peak PSS (MiB) | 528 (1%) | 91 (5%) | 5.8x |
| Peak RSS sum (MiB) | 1,403 | 94 | 14.9x |
| memory.peak (MiB) | 398 | 86 | 4.6x |
| Processes | 15 | 1 |
The Chrome driver is a separate Node process and is not in the Chrome columns. It added 0.28 s of CPU time and 76 MiB of memory to each run.
VIMethod and limits
One machine: AMD Ryzen 9 5900HX, 16 threads, Linux 7.2. Each browser ran in its own cgroup. CPU time and memory peaks come from the cgroup, user instructions from perf stat, and PSS from a sampler every 20 ms. Window runs used an isolated headless Wayland compositor, so no run touched the desktop.
Before the runs, I paused every other workload on the machine: other agents, 29 containers, a virtual machine, timers and file sync. Load average stayed between 0.3 and 0.9. The runs alternated between the two browsers, 6 pairs headless and 4 pairs in a window.
Not tested. A second machine, more runs, a real desktop window, a warm Chrome cache between runs (each Chrome run used a fresh profile), and Playwright itself. Wall times depend on the network and the staging server. The instruction counts are the most repeatable numbers.