Hi Scott,
MaxInlineSize (default 35) is the size under which methods will be inlined
regardless of whether they meet the "hot" criteria (number of invocations
observed; 10,000 for server VM).
FreqInlineSize (default 325 on Linux x86_64) is the size up to which
HotSpot will inline methods if they
JITWatch looks like an interesting project.
Where did you get the information about the 325 byte limit? The data I found
indicated that the default limit was *much* smaller.
From this page:
http://docs.oracle.com/javase/8/docs/technotes/tools/windows/java.html#BABDDFII
-XX:MaxInlineSize=size
Hi Chris,
I’ve not seen any experiments or investigation along these lines, looking
forward to what you find!
Richard
> On Nov 3, 2014, at 3:42 PM, Chris Newland wrote:
>
> Hi all,
>
> As part of the JITWatch[1] project I've written a tool called JarScan
> which counts the bytecode size of m
Hi all,
As part of the JITWatch[1] project I've written a tool called JarScan
which counts the bytecode size of methods in a jar and logs those methods
which are above HotSpot's 325 byte size threshold for inlining methods it
determines are "hot".
In jfxrt.jar from Oracle's JDK 1.8.0_25 on Linux
