3 ms·
I have plenty of anecdata to share on this confirming Safari is generally lighter, and for common usage that should be pretty reliable. But from the same anecd
by eyelidlessness 6y ago
I have plenty of anecdata to share on this confirming Safari is generally lighter, and for common usage that should be pretty reliable.
But from the same anecdata experience, what happens when it’s not is awful.
So the significant difference between Safari’s and Chrome’s model is how tabs are pooled into subprocesses. Safari quickly groups same-origin tabs into the same process which has a huge memory cost advantage. Chrome very aggressively spawns subprocesses per tab up to some pressure metric before it starts sharing processes across tabs, which consumes more memory but much more readily frees it too.
Safari’s model is basically more shrewd and probably better for average users, but the pathological case is GBs of unused memory with unclear priority and total system stalls. Chrome’s pathological case is much easier to reach but much easier to recover from because for the most part closing or killing a bad tab process fully relieves its resource pressure.