Permalink
ce2564f Nov 21, 2017
1 contributor

Users who have contributed to this file

61 lines (43 sloc) 2.83 KB

Iris vs .NET Core(C#) vs Node.js (Express)]

Hardware

  • Processor: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz
  • RAM: 8.00 GB

Software

Go ahead to the README.md and read how you can reproduce the benchmarks. Don't be scary it's actually very easy, you can do these things as well!

Results

  • Throughput - bigger is better.
  • Reqs/sec (Requests Per Second in Average) - bigger is better.
  • Latency - smaller is better.
  • Time To Complete - smaller is better.
  • Total Requests in this fortune are all 1 million, in order to be easier to do the graph later on.

Native

Name Throughput Reqs/sec Latency Time To Complete Total Requests
Iris 29.31MB/s 157628 791.58us 6s 1000000
Kestrel 25.28MB/s 139642 0.89ms 7s 1000000
Node.js 13.69MB/s 50907 2.45ms 19s 1000000
Iris with Sessions 22.37MB/s 71922 1.74ms 14s 1000000
Kestrel with Sessions 14.51MB/s 31102 4.02ms 32s 1000000
Node.js with Sessions 5.08MB/s 19358 6.48ms 51s 1000000

each test has its own screenshot, click here to explore

MVC (Model View Controller)

Name Throughput Reqs/sec Latency Time To Complete Total Requests
Iris MVC 26.39MB/s 141868 0.88ms 7s 1000000
.Net Core MVC 11.99MB/s 54418 2.30ms 18s 1000000
- - - - - -
Iris MVC with Templates 136.58MB/s 18933 6.60ms 52s 1000000
.Net Core MVC with Templates 88.95MB/s 12347 10.12ms 1m21s 1000000
- - - - - -

nodejs express does not contain any MVC features

Updates

  • 21 November 2017: initial run and publish

Articles (ms windows OS)

Thank you all for the 100% green feedback, have fun!