The same set of business logic, implementing a WebService intermediate interface, involving memcached and mogodb some operations.
implemented separately in node. JS and the Java platform, Java code is deployed on Tomcat 7.0 and tested with Apache JMeter for stress testing.
The resulting test results are surprisingly, why is node. JS's high concurrency advantage not reflected???
Operating system: CentOS 6.4 (virtual machine)
Memory: 1.5G
CPU: Single Core
Number of concurrent 100
Number of executions 10
Here are the test results
You can see that node. js has an average execution time of 333 milliseconds, Tomcat executes 48 milliseconds, and Tomcat is nearly 7 times times faster than node. js!
Add: Even if the Test interface is returned directly, and no subsequent operations are involved, Tomcat is more than n times faster than node. js, and there is no explanation for the relevant tests.