Thanks Mike and Ricardo. That explains. I've seen various strategies implemented at WebCacheManager::ReviseAllocationStrategy which effectively manage the caching mechanism. Thanks for the explanation.
Regards, Amruth Raj. On Thu, May 20, 2010 at 5:16 AM, Mike Belshe <mbel...@google.com> wrote: > On Wed, May 19, 2010 at 12:53 AM, ARaj <araj2...@gmail.com> wrote: >> >> Hi, >> In one of the design docs, it is mentioned that there is a 32MB shared >> in-memory-cache pool maintained across all the processes. >> So, is it maintained by the Browser process? > > I think you're referring to the WebKit cache, which is in the renderer > processes. > >> >> If so, how are each of >> the CachedResources which are present in the RenderProcess transferred >> to Browser process. > > They are not. The browser merely tells each renderer what size to adjust > its cache size to. Initially, with one tab, it gets the full 32MB. As you > add more tabs, the 32MB gets shared among them. The policy for how much > memory each tab gets varies based on the number of tabs and which tabs are > visible. This could definitely be improved, and we have seen cases where a > page performs much better when there are fewer tabs active. > >> >> Can someone please point me to the code which implements this. > > render_process_host.cc? (I think) > Mike > >> >> Regards, >> Amruth Raj. >> >> -- >> Chromium Developers mailing list: chromium-dev@googlegroups.com >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-dev > > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
