[Webkit-unassigned] [Bug 98539] Refactor resource loading to allow for out-of-process loading and memory caching

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=98539





--- Comment #6 from Adam Barth <abarth at webkit.org>  2012-10-05 11:43:11 PST ---
> Net loss in what regard?  Memory use?  Performance?  Etc?  Please share data if you have it.

We conducted the experiments in 2007 and then again in 2009.  I don't think we have the data around anymore.

> Experimentally we know that running multiple WebProcesses with individual caches uses unacceptably more memory and - without disk caching - leads to slower page load speeds.

Yes, that's correct.  The approach we use in Chromium is to have a global budget for memory cache.  We then apportion the budget to the various render processes based on a number of heuristics.  For example, foreground render processes get a bigger budget than background processes.  When a process is moved to the background, we ask it to reduce its memory cache usage if the budget is tight.  See

http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/web_cache_manager.h
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/web_cache_manager.cc

for details.

As I recall, the experiments we ran showed that there wasn't much duplication of cached items across render processes, so it wasn't worth using shared memory to unify the caches.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.