JRuby JIT should have an upper limit on how many methods can be compiled, to
avoid eating too much permgen
----------------------------------------------------------------------------------------------------------
Key: JRUBY-1798
URL: http://jira.codehaus.org/browse/JRUBY-1798
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Charles Oliver Nutter
Fix For: JRuby 1.1
Currently, JIT will continue compiling methods as the application runs ad
infinatum. However the biggest perf improvements will come from those methods
compiled during the early phases of an application run. To avoid generating
classes infinitely, there should be a configurable upper limit on how many
methods to JIT.
Note that the current model doesn't necessarily mean it's leaking classes,
since they should be generated into their own classloaders and be
garbage-collectable. However it does mean that JRuby's permgen load tends to be
far higher than other Java apps and probably a lot higher than it needs to be
for maximum benefit.
--
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
