Updates:
Owner: [email protected]
Cc: [email protected] [email protected]
Comment #5 on issue 3539 by [email protected]: Page reload slows the
ray tracer code down by 3-4x
https://code.google.com/p/v8/issues/detail?id=3539
Important feedback was being cleared. When we made this stop in a private
build, the feedback went megamorphic, which was just as bad for
performance. Doh!
We have a two pronged approach to fixing it, both alone will repair the
issue, but both together maximize generality of the fix:
a) Vector3f is a global name, and we don't really need a feedback slot for
it. Alter compilation to eliminate the feedback at this point. (Toon will
do this).
b) Constructor calls are the last place where we still clear feedback with
a sledgehammer on every gc. The reason is that they embed JSFunctions in
the feedback vector and can't risk a memory leak. They should embed weak
cells instead, so we don't have to clear so often. At the same time, we do
need to clear those slots when retrieving code from the cache on a new
context. This brings vector slot handling into the same behavior as vector
IC slot handling. (I'll do this).
--
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.
