Examine each deoptimization case in ASTInspector to see if it's still valid or
could be eliminated
--------------------------------------------------------------------------------------------------
Key: JRUBY-2853
URL: http://jira.codehaus.org/browse/JRUBY-2853
Project: JRuby
Issue Type: Bug
Components: Compiler
Affects Versions: JRuby 1.1.3
Reporter: Charles Oliver Nutter
Assignee: Charles Oliver Nutter
Priority: Blocker
Fix For: JRuby 1.1.4
I discovered today that for some time local variable assignment was causing
method bodies to always be heap-based. This is likely the source of a lot of
performance issues and memory pressure in previous releases, including JRuby
1.1.3. As a result, I think it's absolutely critical that we do two things
immediately:
# Finish creating benchmarks for all logical paths through all AST nodes, so we
have a set of tests we can run to look for regressions and measure improvement
# Examine all cases in the compiler where different AST nodes cause different
types of deoptimization, and clearly document or eliminate those cases
Given the severity of this local variable issue, I suspect there are many other
performance faults hiding in the compiler and the AST inspection process.
Suggestions for how to start also adding unit tests that confirm we're
correctly compiling or correctly inspecting the AST are also welcome.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
