4 ms·
Assuming a commercial web application, appropriately sized hardware, and correctly optimized code, when is "footprint" a significant disadvantage? How is "footp
by bmh100 10y ago
Assuming a commercial web application, appropriately sized hardware, and correctly optimized code, when is "footprint" a significant disadvantage? How is "footprint" defined? When are startup times a significant disadvantage?
- macco 10y agoIf you use Rasberry Pi, real-time web apps. In most use cases the jvm will be superior.
- auvrw 10y agohere, footprint is 'memory footprint,' the amount of main memory used by the application. this is useful b/c VPSes are priced mostly based on memory ----- i like that this says it's mostly trying to be "ring for node" ..
- ledgerdev 10y agoHere's a couple significant disadvantages to the jvm. A simple jvm clojure app running jetting deployed as an uberjar takes about 12 seconds to start on a 1GB digital ocean vm. Using jvm clojure as with aws lambda, it takes ~20 seconds for a cold start. Normal java is typically a couple of seconds, and it's likely that a cljs/node instance will be sub-second cold start.
- dskrvk 10y agoNote that with Lambda a cold start doesn't have to happen every time - if the function is executed frequently enough, the application will be kept around on the executing node. Also, if your application has fairly stable load, then startup times are irrelevant 99% of the time, since you can just run persistent servers.