Reviewers: ulan,
Description:
Implement caching scheme for Date fields.
This is based on https://chromiumcodereview.appspot.com/9117034/
Unfortunately, the impact of this change is almost 0. I tried various
variations
and degrees of laziness in caching vs aggressiveness in precomputing. Being
more
agressive is a win on one benchmark but a much bigger loss on the other,
whereas
being more lazy eliminates the losses, but also the wins. :( In the end,
the
scheme I uploaded with this CL has the best overall performance, but is at
most
1-2ms better overall than the old representation (which is below noise
level).
Consequently, I'm leaning towards not committing the Date changes, unless
somebody comes up with a clever idea for improving what I have.
[email protected]
BUG=
TEST=
Please review this at https://chromiumcodereview.appspot.com/9307083/
SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge
Affected files:
M src/api.cc
M src/date.js
M src/macros.py
M src/objects-debug.cc
M src/objects-inl.h
M src/objects-printer.cc
M src/objects.h
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
