On Thu, Oct 1, 2009 at 12:38 PM, Scott Hess <sh...@chromium.org> wrote:
>
> On Thu, Oct 1, 2009 at 11:32 AM, Mike Belshe <mbel...@google.com> wrote:
> > On Thu, Oct 1, 2009 at 11:27 AM, Scott Hess <sh...@chromium.org> wrote:
> >> Could we set jemalloc on selected renderer processes? I realize that
> >> wouldn't necessarily only impact the target domains, but it might be
> >> better than making the change global.
> >
> > It can be set by a per-process environment variable. So... yes, this
> could
> > be done. Mix-and-match allocators might be a little strange for anything
> > other than debugging/testing.
>
> I was thinking enabling for the gmail renderer (and whoever gets stuck
> in that process) might be more useful than enabling for everyone - but
> obviously we'd need ways to identify the source of any uploaded data.
>
> That said, being able to enable alternate malloc libraries in the
> browser process might have relatively low performance costs compared
> to the value of the data generated. I don't mean to imply that
> browser-process performance is not important, but rather that race
> conditions and double-frees and the like are much more dangerous
> there. Also, interpreting the data would probably be easier (renderer
> data and browser results would be internally consistent).
>
Both of these points seem like big wins to me, for what it's worth.
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
