3 ms·
"Node is nimble; for example, we advise our clients to kill & quickly restart when their applications enter an unexpected-error state. You can’t do this with a
by StillBored 12y ago
"Node is nimble; for example, we advise our clients to kill & quickly restart when their applications enter an unexpected-error state. You can’t do this with a runtime that takes minutes to properly start and warm-up."
Hmmm. I'm running tiddlywiki (node.js app) on an ARM, and it probably takes a good ~30 seconds to start up.. Not good for an application that weighs in at 20k lines of code, 3/4 of which isn't even javascript. Worse yet, it has noticeable delays during operation, including about a 15 second delay if it hasn't been accessed in a few hours. I might blame it on a big dataset, but frankly it has less than a 100 tiddlers, and everthing is hosted on a SSD. This on a machine that generally is quite responsive, and capable (although its about 1/5 as fast as my desktop in some benchmarks I ran). It sure doesn't take that long to start apache/php on the same machine and start serving pages.
- tracker1 12y agoI am surprised that your application takes 30 seconds to start up in node. I have several utility scripts that run via babel-node instead of pre-build that don't take that long to start. When running pre-built JS, even using next generation syntax in source the start up is usually well under a second... Most of the lag time is in initializing database connection pools. That said, how large is your application? Can it be broken up in to more right-sized services? Are you maintaining a lot of instantiated objects in scope? Are you using OO or FP orchestration? What kind of application is it? (edited to be less abbrasive)