Status: Untriaged
Owner: ----
New issue 4209 by [email protected]: AdjustAmountOfExternalAllocatedMemory
should try to trigger scavenges
https://code.google.com/p/v8/issues/detail?id=4209
See https://github.com/nodejs/io.js/issues/1671 and testcases at
https://groups.google.com/forum/#!topic/v8-users/7bg5ym8t7KU and
https://github.com/nodejs/io.js/pull/2022#issuecomment-113769435.
Atm, it looks like ArrayBuffer objects (and hence typed arrays) are
collectable with scavenges, but they do not trigger scavenges themselves.
If you run a simple testcase (provided in the above links) that creates
(and does not store references to) a lot of ArrayBuffer instances, you will
see that only mark-sweeps are run, that the peak memory usage goes above
400 MiB, and there is much time spent on mark-sweeps.
But those objects are collectable by scavenges, so if you make it run
scavenges instead (for example slicing an unrelated array) that could speed
up the testcase (as you can see at the links above) and lower the peak
memory usage an order of magnitude (to 40 MiB).
The correct solution would be to try to run scavenges first to free the
externally allocated memory.
I expect that result in lowering the peak memory usage of my testcase at
least 10 times and an about 2x speedup.
--
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.
