Comment #2 on issue 4014 by [email protected]: ES6 Map performance issues
https://code.google.com/p/v8/issues/detail?id=4014
First benchmark populates the Map with non-internalized strings as keys and
then uses internalized strings to lookup. This favors object case (which
internally internalizes keys) and penalizes Map case which does not.
Using internalized strings to populate the map improves performance:
http://jsperf.com/gwt-es6-map-vs-object-properties/3 there is still a
factor of 2x missing though, which is not unexpected given that object is
like a dictionary which is known to contain only internalized strings and
symbols as keys - which makes it much cheaper to probe.
@arv: I think JS version that was landed recently is actually slightly
slower on this benchmarks than the previous implementation.
--
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.
