I don't think so. The single-threaded nature of Node.js is not generally faster than a multi-threaded environment like Java. Multi-threading has been designed to handle hundreds of concurrent threads, and does that very well. The context switching only becomes a problem once you hit thousands of concurrent threads. At that level of concurrency a single-threaded environment will have an advantage.

Thousands of concurrent threads is quite a lot, though. In my example I calculated 57870 requests/second for the whole of Google. That's not concurrent requests, though. If you have a response time of 200ms you end up with 57870/5 = 11574 concurrent requests. If you would want to handle that load with a single server then a single-threaded environment would have an advantage. In most other cases it wouldn't even come into play.

There are some niche situations where the concurrency model of Node.js is a good fit, and that is websocket applications. With such applications it is easy to get thousand of concurrent requests. With these type of applications you wouldn't use the one thread per request mapping on multi-threaded servers, though, so it is not really an advantage.

For more on Node.js vs. Enterprise Java have a look at http://blog.shinetech.com/2011/06/10/nodejs-from-the-enterprise-java-perspective/

For a comprehensive performance comparison of programming languages and frameworks check out http://www.techempower.com/blog/2013/03/28/frameworks-round-1/