quick-tips-optimizing-jvm.md


24 bookmarks. First posted by skchrko 26 days ago.


I was talking to a coworker recently about general techniques that almost always form the core of any effort to write very fast, down-to-the-metal hot path code on the JVM, and they pointed out that there really isn't a particularly good place to go for this information. It occurred to me that, really, I had more or less picked up all of it by word of mouth and experience, and there just aren't any good reference sources on the topic. So… here's my word of mouth.
java  programming 
21 days ago by jcrites
The solution here is just to avoid polymorphism in the hot path unless you can be 100% certain beyond any shadow of a doubt that the runtime dispatch receiver types will always be either a single type or one of two types. This of course means that you cannot use abstractions of any kind whatsoever in the hot path, since abstraction by definition means code reuse, and code reuse requires polymorphism, and polymorphism gets us stuck in this whole mud hole. So you're going to end up writing a lot of very manual, very uncomposable boilerplate. This is deeply unfortunate, but it's the price you pay for having a hot path.
jvm  scala  performance 
21 days ago by euler
I was talking to a coworker recently about general techniques that almost always form the core of any effort to write very fast, down-to-the-metal hot path code on the JVM, and they pointed out that there really isn't a particularly good place to go for this information.
java  performance 
25 days ago by nicolashery
RT : Quick tips for optimizing applications on the JVM:
from twitter
25 days ago by rafaeldff
Tips for optimizing the hot path.
jvm  java  scala  tips  performance 
25 days ago by bkittelmann
Quick tips for optimizing applications on the JVM:
from twitter_favs
26 days ago by skchrko