Comment #2 on issue 3907 by [email protected]: Allowing asm.js memory
growth causes big slowdown
https://code.google.com/p/v8/issues/detail?id=3907
The typed array must be replaced to change its size. This should happen
rarely or not at all - we double the size each time it grows. Is the issue
here that it *does* happen, or that it *could* happen? I assume - Boris,
can you confirm? - that it doesn't happen in practice on this testcase, as
the only change is that growth is flipped on or off, and it works without
growth - i.e., the initial size is big enough, without an actual growth
event.
Please let me know if this option being on by default in emscripten is a
concern for you - we just turned the default to on (on the bleeding edge
branch), but I can reverse that.
Note that this is valid asm.js, heap replacement was added a while ago,
http://discourse.specifiction.org/t/request-for-comments-switching-resizing-heaps-in-asm-js/641
--
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.
