RingoJS is not slow. We use it in the Erbix backend, running a separate Rhino/RingoJS engine for each account. It's really stable, fast, multi-threaded.
We use it in conjunction with PostgreSQL JDBC driver, serving large source code files, rendering templates written in JavaScript, static files upload/download, etc.
If you are running Apache Tomcat (or anything based on Coyote), as I can see from headers, you are _already_ serving slower than Node. Just because Tomcat needs more time to parse and return the response than Node. Only Jetty with NIO connector has comparably high speed. (Yes, I've tested by myself).
And, JFYI, you have to move static content to nginx or lighthttpd, Coyote serves static files even worse than Apache web server.
All you say about functionality of the platform has no relation to the speed.
We use it in conjunction with PostgreSQL JDBC driver, serving large source code files, rendering templates written in JavaScript, static files upload/download, etc.
http://www.erbix.com is an Erbix app running on a standard Erbix account.