Comment #4 on issue 3626 by [email protected]: start with a large heap
reservation and shrink if it's not utilized
https://code.google.com/p/v8/issues/detail?id=3626
we observed that during page load, we see a number of expensive scavenges
(i.e. with a high survival rate) and that the data later dies.
We want to explore starting with a larger new space hoping that by the time
we scavenge, the data is already garbage.
Now just starting with a large new space will waste a lot of memory on
pages that don't run javascript at all. Instead, we gradually commit
additional pages until the "target capacity" at which point we do a
scavenge and continue with the regular growth strategy.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
