Tagged memory
2 write-ups.
Measuring the Wrong Process for Eight Months
My benchmark credited each tab with one process and counted every other process as nothing. Re-measured against every process the browser actually owns, the light-pages result inverts: the ladder I published as 2.63x better than doing nothing is 1.35x worse.
What a Hibernated Browser Tab Actually Costs
My simulated tab scheduler priced a hibernated tab at 32 KB; real WebKit charges 39 MB. It claimed 7.9–11.5x less memory than an unmanaged browser and delivered 1.4–2.6x. That one number, wrong by three orders of magnitude, explains the entire gap.