You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simplify this method and reduce its length to bring its bytecode length under 325 bytes (-XX:FreqInlineSize=325) to give it a better chance of being inlined during JIT compilation.
Before
Before this change the lock method had a bytecode length greater than 325 bytes. A benchmark was setup to run an appender in a tight loop ensuring sufficient time for compilation. The compilation log was captured including inlining information. The only methods that were inlined from within the TableStoreWriteLock class are shown below - note that lock was not inlined:
After
After the refactor of the lock method and its new associated sub-methods the same benchmark was re-run and we can observe lock being appropriately inlined:
The output of jclasslib showing the length of the bytecode is shown below:
The text was updated successfully, but these errors were encountered:
Simplify this method and reduce its length to bring its bytecode length under 325 bytes (-XX:FreqInlineSize=325) to give it a better chance of being inlined during JIT compilation.
Before
Before this change the
lock
method had a bytecode length greater than 325 bytes. A benchmark was setup to run an appender in a tight loop ensuring sufficient time for compilation. The compilation log was captured including inlining information. The only methods that were inlined from within theTableStoreWriteLock
class are shown below - note thatlock
was not inlined:After
After the refactor of the
lock
method and its new associated sub-methods the same benchmark was re-run and we can observelock
being appropriately inlined:The output of jclasslib showing the length of the bytecode is shown below:
The text was updated successfully, but these errors were encountered: