Methods hot but too big for inline

[normanmaurer]

While doing some benchmarks I noticed there are a few methods that are hot but are to big for the JIT to inline. We should check if we could do a better job here and optimize them for the most common usage in terms of size etc.

This way the JIT can make inline happen:

@ 25   io.netty.handler.codec.http.HttpObjectDecoder::decode (1159 bytes)   hot method too big
@ 17   io.netty.channel.ChannelOutboundBuffer::nioBuffers (360 bytes)   hot method too big                              @ 25   io.netty.handler.codec.http.HttpObjectEncoder::encode (458 bytes)   hot method too big
@ 14   io.netty.handler.codec.http.HttpObjectDecoder::parseHeaders (525 bytes)   hot method too big
@ 110   io.netty.handler.codec.http.HttpObjectDecoder::splitInitialLine (399 bytes)   hot method too big
@ 42   io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe::read (729 bytes)   hot method too big
@ 25   io.netty.handler.codec.http.HttpObjectEncoder::encode (458 bytes)   hot method too big

[trustin]

Out of curiosity, how did you get this data?

[normanmaurer]

@trustin start with "-XX:+PrintCompilation -XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining" and check the generated outpout. Best is to direct it to some file as it will be quite "heavy" ;)

Related blog post: http://techblug.wordpress.com/2013/08/19/java-jit-compiler-inlining/

[trustin]

Ah, Thanks.

[jestan]

Nice findings @normanmaurer :)

[CodeMason]

Indeed - that's very nice!

On Thu, Sep 5, 2013 at 7:47 AM, Jestan Nirojan notifications@github.comwrote:

Nice findings @normanmaurer https://github.com/normanmaurer :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1812#issuecomment-23861940
.

[helloworld2688]

how interesting