History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRUBY-2555
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Charles Oliver Nutter
Reporter: Charles Oliver Nutter
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JRuby

CLONE -JIT max and JIT threshold should be adjusted for improvements in JRuby over the past months

Created: 23/May/08 04:18 AM   Updated: 23/May/08 04:19 AM
Component/s: Compiler
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified


 Description  « Hide
We have long talked about two changes, which probably should happen now:
  • Bump the JIT max (maximum number of methods that will JIT) up from its current default of 2048
  • Bump the JIT threshold (number of times a method must be called before it will JIT) up from its current default of 20

I will shortly commit changes that makes these 4096 and 50, respectively, but we should have some discussion about what the actual values should be. A threshold of 50 will slightly reduce the number of methods that jit in a typical application, or at least delay the jitting of some methods. The limit of 4096 will allow more methods to JIT, and reflects a steady improvement in the size of compiled code since the 1.1RC2 release where the JIT max was introduced. We could probably go even higher, but we need some empirical data from a real-world app...ideally a Rails app.

Marking as a 1.1.2 blocker, so we can finally discuss and make this change.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Charles Oliver Nutter - 23/May/08 04:19 AM
Cloned to ensure we revisit this issue again after 1.1.2 and try to gather metrics about total class sizes in memory and effectiveness of 4096 JIT max versus other values.