Updates:
Status: Available
Cc: [email protected] [email protected]
Labels: Area-Runtime
Comment #1 on issue 4335 by [email protected]: large google maps
performance regression in chrome canary (version 46)
https://code.google.com/p/v8/issues/detail?id=4335
"non-standard elements" are elements with non-standard attributes, e.g.
read-only elements, or elements of frozen objects. (And by "elements", we
mean "properties with uint32 keys".) All these cases force V8 off the fast
path.
Based on your description, I'm guessing you're running into the one other
situation that also forces the slow path, and that's keys larger
than "static const uint32_t kRequiresSlowElementsLimit = (1 << 29) - 1;".
Can you avoid those? If not, can you get by with a small number of objects
with such keys, and prepare them (store the first large key) very early on
in your app? (Reasoning: transitioning an object to forced-slow-elements is
expensive. There's probably something we can do about that, but it might be
a lot of work.)
If you send me [a link to] the d8 repro I can take a closer look at what's
going on.
--
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.
