Notices

Originally Posted by coffeedrinker

Well, isn't putting each on in its own process and each one having its own interface essentially just running multiple instances, but under one main window?

I spawn multiple copies of links rather than use one process with several windows. Then when I close that "tab" all the memory is reclaimed and I don't have to worry about any cached pages.

browserd, I think, is just the opposite. It is one rendering engine with the ability to respawn the main window. Closing the window doesn't even have any effect on the browser. Am I understanding this correctly?

Originally Posted by epage

Fork is the main way of creating new processes on Linux. When you fork a process, it does not duplicate all of the memory pages but instead marks them as needing to be copied on the next write. If writes never happens or are rare, than very little memory is spent in having two processes. Also on Linux, threads are implemented through processes that share the same memory pages.
http://linux.about.com/od/commands/l/blcmdl2_fork.htm

So in theory, if there are very few changes to the pages of a virgin webkit and that there is little in common between once rendering pages, then the overhead of separate processes would be negligible.

Disclaimer: I do not know details of browserd. I have no clue what benefits it might have by what structure it might use.

Originally Posted by andrewfblack

First itT post on google chrome!
itT runs faster on this I swear.