Thanks for your input, it was just something i tried to reduce the CPU load, and it seemed to reduce it a MINUTE amount. So i kept it in there.. i was kind of aware the JVM might due these optimisations on the fly when executing the classes, but not to sure, so i tried it.

Anyway as i said, it seemed to make a diff so i left it in there..

Working on something atm to make it faster again (thanks to romain for the tips), hopefully i’ll get it up here in a few days (if i get time to work on it) and yeah.. I’ll clean that mess up before i stick it up for everyone to view this time. Only thought about how messy my coding is over the weekend when i was sitting at home looking at it.

That right shift vs. divide by 2 thing so old it’s a meaningless optimization. In the way old days of C compilers this may have had some effect. But compilers since the mid-80′s have had good optimizers that know the instruction sets of our CPUs far better than we do. The optimizers translate an internal representation of the code into the best instructions taking into account global register allocation, pipelining, and the execution cost of each instruction.

Instead of obfuscating the code with this stuff just make the code readable.