I figure by the use cases node is designed for that it would have much less overhead than python would when starting up. But can anyone confirm this by way of experience or benchmarks.
The reason I ask is I'm working on a project in which we are starting many, ~20, python scripts every minute. In these processes we are doing tons of IO with databases and the network. This is a place node would shine, so I want to explore the benefits of possibly using node over python here. I know I could use twisted here to do my i/o asynchronously, but I still need to start these processes up every minute.
Edit:
I know that its not always seen as ideal to start processes like described here. But in this architecture for this system this is the ideal solution. This is why I consider node. Because V8 is event driven only, calling "node myscript.js" at a rate of 20/min shouldn't matter. Calling myscript.js IS the event. Its just not in the browser anymore. [edit] Totally Wrong
After driving to work and thinking about this, I guess my question should have been about how best to benchmark code. From there I could profile both designs.
Update:
brandizzi showed me my err. Doing 'node myscript.js' is NOT the event. And in the end, the node interpreter does take a little longer to start than python. However, that amount is pretty much nothing.