Updates:
Status: Assigned
Comment #4 on issue 24468 by [email protected]: Tune V8 instance in
ProxyResolver to use as little memory as possible
http://code.google.com/p/chromium/issues/detail?id=24468
Mike, I will have a look at this. It is correct that we currently cannot
handle a
different max young space size when using snapshotting. This is because
generated
code in the snapshot (for the write barrier) relies on a mask that depends
on the max
new space size to determine if something is in new space. I can split this
into two
parts. A max new space size used for aligning the new space and another
max which is
the max amount of memory that we will ever *commit* for new space. The
amount of
virtual memory reserved will be the same, but we can limit the amount of
memory
committed (but we cannot set a max young space size that is larger than the
one we had
at snapshotting time - which is not a problem for this scenario).
Jim, new and old space are not similarly sized. Old space grows as needed
up to a
(large) max size. However, I think what you are seeing here is a
*reservation* of a
32MB chuck of memory for new space. The max semi-space size is 8MB which
means that
the max new space size is 16MB for two semi-spaces. We need to align new
space (for
our write-barrier implementation) and therefore we need to *reserve* twice
the amount
of memory (32MB). However, we only *commit* very little of that memory in
the
beginning.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
