JAX: Java performance myths # This talk was one of the famous talks on Java performance myths by Arno Haase. His main point - supported with dozens of illustrative examples was for software developers to stop trusting in word of mouth, cargo cult like myths that are abundant among engineers. Again the goal should be to write readable code above all - for one the Java compiler and JIT are great at optimising. ...
JAX: Does parallel equal performant? # In general there is a tendency to set parallel implementations to being equal to performant implementations. Except in the really naive case there is always going to be some overhead due to scheduling work, managing memory sharing and network communication overhead. Essentially that knowledge is reflected in Amdahl’s law (the amount of serial work limits the benefit from running parts of your implementation in parallel, http://en. ...
JAX: Pigs, snakes and deaths by 1k cuts # In his talk on performance problems Rainer Schuppe gave a great introduction to which kinds of performance problems can be observed in production and how to best root-cause them. Simply put performance issues usually arise due to a difference in either data volumn, concurrency levels or resource usage between the dev, qa and production environments. The tooling to uncover and explain them is pretty well known: ...
JAX: Java HPC by Norman Maurer # For slides see also: Speakerdeck: High performance networking on the JVM Norman started his talk clarifying what he means by high scale: Anything above 1000 concurrent connections in his talk are considered high scale, anything below 100 concurrent connections is fine to be handled with threads and blocking IO. Before tuning anything, make sure to measure if you have any problem at ...
Devoxx – Day one – Java, Performance and Devops # In his keynote Mark Reinhold provided some information on the very interesting features to be included in the Java 7 release. Generics will be easier to declare with the diamond operator. Nested try-finally constructs that are nowadays needed to safely close resources will no longer be necessary – their will be the option of implementing a Closeable interface supporting a method close() that get’s called whenever objects of that class’s type go out of scope. ...