I've noticed a few people in the forums have confused the JVM (for bytecode) with a compiler for native arch. Java's overhead is a bugbear for me because my machines lack the horsepower to even run an idle Spigot server without getting hot enough to fry an egg. My guess is this is not Spigot's fault, but the underlying JVM JIT compiler. Without getting into a long discussion about pros/cons of each method (because I'm sure everyone has an opinion and it's all been argued before and will be again...): Is it possible to used GCJ to compile Spigot into a native app? Not being a developer this is beyond me except that I've read that GCJ can compile both Java byte-code and Java source code into native machine language. This has got to be a good thing for little servers like Raspberry PI and its multitude of clones. I've tried a C++ server vs Spigot and the difference is enough to burn a careless pinkie: even idling Java is loading the machine quite hard and pushing the core temp into the high 50s (celsius) - even with a heatsink. Once again, I don't feel this is a fault of Spigot, purely of the technology it's running on. I think of it as riding atop tank when you could be riding a motorbike: with the same engine!