Peter,
I am aware there will be synchronization issues. I am a grad student who has
been studying concurrent and lock-free data structures for a while now. I'm
actually hoping to apply some of my research in Chromium as a proof of
concept.
I'm also interested in looking into state that is already shared but makes
excessive use of locking and may be hindering performance. Any shared state
applying iterators of some kind would be interesting as well for me.
Thanks,
Fady
On Mon, Jan 4, 2010 at 8:02 PM, Peter Kasting <pkast...@google.com> wrote:
> On Mon, Jan 4, 2010 at 4:58 PM, Darin Fisher <da...@chromium.org> wrote:
>
>> There are some caches in webkit (the resource cache in particular, but
>> there are others) that would be nice to share between processes.
>
>
> If you look into this, note that there are major tricky issues here around
> synchronization if you start trying to share caches between processes
> without hammering perf.
>
> Also, the gain from sharing these will not necessarily be large, for two
> reasons:
> * We already set a fairly small global size limit for the sum of all
> resource caches (and the other caches are pretty trivial)
> * Renderers in separate processes are very likely to be on separate sites
> and have mostly disjoint cacheable sets
>
> PK
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
