View Single Post
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#14
The strength of Google's concept is that every tab is isolated from the rest by running as an own process. On the NIT, however, you don't have that much RAM available, so that it's better to have all tabs running in once process sharing as much resources as possible. That's why Nokia introduced "browserd".
How large is the overhead in reality? The binary code will be shared anyway as presumably it will mainly be located in a shared lib (to allow just this effect), then there's the per-process data which would otherwise be shared between the tabs - stuff like the menu items, window data/theme stuff, etc.

So how large would the extra overhead really be? I always thought the main disadvantage of using processes vs. threads is in communicating across them, which in this case shouldn't be a major thing as each "tab" would not really need to do much IPC.
 

The Following 2 Users Say Thank You to lardman For This Useful Post: