I tried it on daedalus
After resolving some tricky issues, I managed to have daedalus running and fully functionnal.
Concerning the size, it’s pretty interesting : the exe is only 9 Mb in my case, add to this 1 Mb of natives + 20Mb of resources, the result is 30 Mb for the whole game … compared to 28 Mb for the executable jar ( meaning without the jvm … ).
For the performance, I ran daedalus without vsync and without FPS limit. I ran a particular case where I know that I’m CPU limited and got better results with the JVM (1.6) … this has to be taken carrefully as I’m testing ingame so the context might be a bit different between two runs …
My test was to have 16 bots playing in a very small map … generating a lot of blood I was looking at the time taken to compute a frame with about 2500 alive blood particles. With the JVM it was 9/10 ms and with the exe it was more 12ms.
So I’m a bit disapointed here
Then concerning the time to run the application, it is a bit faster with the exe but not much: about 500ms on a total load time of 5 seconds … so not much
So at the end, the only gain here for me is the reduced size on disk, and the obfuscated code. The size is not really important for my game, as it should be quite big at the end, so the embedded JVM will not represent 90% of the size
I don’t know if I’ll be using it for daedalus, I’m already using launch4j to generate an exe which is working quite well …
But for a small game I think it could be quite cool … particularly for the size of the exe
EDIT :
I fully agree
Also I forgot but it seems that this software can generate an installer as well … making it even more interesting