Node.js 벤치마킹 펌.

http://zgadzaj.com/benchmarking-nodejs-basic-performance-tests-against-apache-php


  • Total request: 100,000; concurrency level: 1,000
    • node : Requests per second: 4725.43 [#/sec] (mean)
    • apaceh : Requests per second: 823.38 [#/sec] (mean)
  • Total requests: 1,000,000; concurrency level: 20,000
    • node : Requests per second: 958.70 [#/sec] (mean)
    • apaceh : Requests per second: 280.05 [#/sec] (mean)
  • 비율 : 5.7 : 1 ~ 3.4 : 1


Conclusions

As the above tests show, node is fast. Really fast. Much faster than Apache - many more requests per second, higher transfer rate with much smaller number of failed requests at the same time. Really shining.
-> node는 띠따 빨라.

Obviously it is more hungry for system's CPU and memory, but this should not be surprising considering its performance.
-> CPU와 메모리 많이 쓰지만 놀라운 성능이잖아!

What needs to be kept in mind though is that everything really depends on what you want to use Node for. As already said in many places, Node is not something that should replace Apache everywhere.

When considering using Node for a new project (or rewriting an old one) absolutely first thing to do is to make sure that Node really is a good fit for it. Also, depending on project's planned features, used libraries, connections with other systems and/or databases, Node performance could be completely different and not that exciting anymore.

The point is - all those tests above are only the very first point of reference - but to make sure that Node really meets your own specific requirements, you need to test your own system yourself.

댓글
  • No Nickname
    No Comment
  • 권한이 없습니다.
    {{m_row.m_nick}}
    -
제목 작성자 날짜
공대여자
공대여자
mins01
공대여자
공대여자
공대여자
공대여자
공대여자
공대여자
공대여자
공대여자