connect

That's not really a valid test. NodeJS can easily make use of multiple cores with child processes, but by design, it's a very low-level API, so that stuff isn't used by the HTTP server by default. In other words, it doesn't assume you want to use multiple processes for your HTTP server. Maybe you want to use them for something else. (Like, if you have an HTTP server and an IRC server sharing the same box, and you want to make sure they are isolated from one another, or something.) Check out http://github.com/kriszyp/multi-node or http://github.com/extjs/Connect for examples of web servers that will blow Clojure out of the water in this benchmark. When leveraging multiple cores, NodeJS is closer to nginx in terms of performance than it is to Jetty or Django. (Of course, nginx uses almost no memory, and NodeJS has this big honkin VM ju

There are also Fab.js http://github.com/jed/fab (which hasn't seen any updates in a while, but I'm sure it's still being worked on), Pintura http://github.com/kriszyp/pintura and Picard http://github.com/dantebronto/picard At a lower level of abstractions are the middleware layers Connect http://github.com/extjs/Connect and JSGI http://github.com/kriszyp/jsgi-node