Updates:
Status: WorkingAsIntended
Comment #2 on issue 3144 by [email protected]: poor performance on
property lookup when the key is the result of a string concat
http://code.google.com/p/v8/issues/detail?id=3144
Accessing properties with an internalized (unique) string as key is a lot
faster than with normal string keys. String literals (such as 'fast_key')
are always internalized right off the parser. Keys that are result of a
concatenation are not immediately internalized. They are though, later on,
when they are tenured (survived a few GCs).
So in your example, 'fast_'+'key' doesn't get the "preferential treatment"
because it's not internalized. If you cause the GC to kick in between
computing the key and actually using it in the property loads, there is no
difference between that and the literal 'fast_key'.
--
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/groups/opt_out.
