Status: Accepted
Owner: [email protected]
Labels: Type-FeatureRequest Priority-Medium
New issue 3415 by erik.corry: Request: Make
AdjustAmountOfExternalAllocatedMemory incremental
http://code.google.com/p/v8/issues/detail?id=3415
The AdjustAmountOfExternalAllocatedMemory API call can trigger a global
stop-the-world GC when external memory reaches a certain limit. The call is
used by Blink's PartitionAlloc heap to help V8 make decisions on when to do
a global GC, and it is planned that it will be used by the new Oilpan (GC
in Blink) heap too.
As it is used more, it would make sense for it to be a little less heavy
handed about its GCs. My suggestion would be to set off an incremental GC
when a limit is reached and to do some incremental GC work when subsequent
calls increase the external memory level. That way we would get regular GCs
on tests like blink_perf ShadowDOM_LargeDistributionWithoutLayout which I
think would dramatically decrease the peak non-V8 heap size. I did a test
with --gc-global, which already helped some.
--
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.
