My understanding is that these sorts of comparisons are basically useless unless you're measuring in a RAM constrained environment. When there's lots of free me

My understanding is that these sorts of comparisons are basically useless unless you're measuring in a RAM constrained environment. When there's lots of free memory, Chrome will cache the hell out of everything to boost performance. Until it's starving other processes IMO that's the right call (the browser creator who ran the original test mentions this but the linked article summarizing his work kinda glosses over that). If you're only opening 2 tabs and have 20 GB of free memory on your machine, you're not measuring how good the browser is at sharing RAM with other programs. (Obligatory disclaimer that I'm a Google shill who has no direct involvement with Chrome and I still do most of my browsing in Firefox)