5 ms·
You can build "fat jars" that contain all dependencies. IMO, this is how most Java apps should be deployed.
by icedchai 8y ago
You can build "fat jars" that contain all dependencies.
IMO, this is how most Java apps should be deployed.
- virmundi 8y agoYou still have issues of needing a JVM. The JVM is not a small runtime considation. I'm in the process of converting to GO since I have more time than money. 1 JVM in Docker uses 512 MB to sit still. A Go version is around 16.
- malkia 8y agoHere is what Google did internally: - Bundle all C/C++ native libraries, and link them all together with the java launcher - e.g you produce your own java.exe that has your C/C++ libraries linked in, then you slap the .jar file - for extra bonus you can slap at the back of your .exe and make it load from there Voila - you have single executable (almost) with all you need, and you don't need to unpack .dll's anywhere But... you must compile java.exe yourself...
- flingo 8y agoJava is somewhat like chrome in that it pre-emptively gets some RAM, because it's managing memory allocation to programs itself. (and because the speed increase of not doing system-calls offsets some of the performance hits from running a JIT) Is that 512 the lowest you can get it with command line options?
- virmundi 8y agoThat was with Xmx set to 64 MB and a stack of 256k
- icedchai 8y agoMostly FUD. You can easily tweak your min and max heap sizes. You can have an app that takes less that 512 megs of RAM.