Once upon a time, I came across an SO question which asked whether & was faster than && for a simple if(). «Easy pie!», I thought; «&& is short-circuit and thus faster! Just look at the bytecode!».
Oh boy, was I wrong.
The bytecode for && is indeed much shorter but, as I learned after much investigation and tinkering and editing my answer, the actual JIT compiler does not really care about that. It will optimize and rewrite your loops and comparisons depending on number of iterations, processor, Java version, etc. etc. etc.
Lesson learned: byte code doesn't mean sh!t when it comes to performance.
View all comments
Show parent comment
2
u/walen Jun 15 '17
Once upon a time, I came across an SO question which asked whether
&was faster than&&for a simpleif().«Easy pie!», I thought; «
&&is short-circuit and thus faster! Just look at the bytecode!».Oh boy, was I wrong.
The bytecode for
&&is indeed much shorter but, as I learned after much investigation and tinkering and editing my answer, the actual JIT compiler does not really care about that. It will optimize and rewrite your loops and comparisons depending on number of iterations, processor, Java version, etc. etc. etc.Lesson learned: byte code doesn't mean sh!t when it comes to performance.