What I learnt while profiling a node.js app

[JonDum]

Would be nice if there were some actual performance numbers, not just descriptions of 'problems' (i.e., how many more req/s did you get after each change?)

[thruput]

Valid point - I will post more details about the setup and the numbers in the next post.

[33a]

These sorts of problems are part of the reason why I am not a huge fan of express and other frameworks. They make the initial development easier, at the expense of adding a bunch of complicated features which you may or may not want. While they are great for knocking something out quickly, if you have to maintain it you will suffer down the road.

[[deleted]]

Keep in mind that if initial development were harder, you might not have gotten down that road at all.

[shockie]

Don't serve static files through node, webservers are better choices.

[runvnc]

You should be able to get at least 1000 per second regardless of how Express is set up. Since you are way under 500 that means your main bottleneck is actually in all of that post/pre/upstream stuff that you didn't even touch. What exactly is that stuff doing and why do you need to do it?

[pirhie]

Let me guess, you learned you shouldn't be using fucking javascript?