Opera is pretty aggressive and intelligent with caching, which gives it a reputation of a memory hog on benchmarks, but it apparently scales back in resource-co

Opera is pretty aggressive and intelligent with caching, which gives it a reputation of a memory hog on benchmarks, but it apparently scales back in resource-constrained environments. To my understanding, Opera caches not just the page code, but the parsed & loaded DOM tree of recent content. This makes for fast go-back times, as well as (sometimes) saving the page state on dynamic pages. That "ought to be" part of the browser, not the renderer, since it's hanging on to content that the renderer is already done with. But I'm not familiar enough with either architecture to answer for certain.