For comparison, if you don't unload the page completely, and system gets into swapping then there will be random access pattern with speed about 400 Kb/s on a HDD. So it is faster to unload 500 Mb sequentially than swap out/in 5 Mb.
2. it's very messy data, it's a bunch of seas of nodes (the DOM, the JS heap, the styling info, etc...)
3. I wouldn't be surprised if it was data which isn't fully isolated (e.g. shared style caches), meaning it first has to be fully forked to resolve into a self-contained bundle
OS have the ability to just freeze and store / restore memory, but I'm not sure they give that capability to use processes.
Image-based systems (smalltalk, self) would probably be a better model for a live tab, but it still requires things to line up.
Anyone have ideas why the tab's memory contents can't be offloaded to SSD and restored instead? Personally I don't like losing state (e.g. filled in forms, scroll position, deleted posts, etc) from using other extensions like Great Suspender.