Performances
Performance is a built-in feature !
Thanks to its architecture, SimpleW can handle the 10K connections problem.
Server Comparison
Monitoring requests-per-second is not relevant as it depend on the hardware.
What matters is how each server performs relative to the others in the same conditions.
Dynamic
Evaluate request with a server containing a single route and returning json object
Results average : 3 runs of bombardier -c 200 -d 30s $url
| Server | Perf (%) | Total (req) | Max (req/s) | Average (req/s) | Min (req/s) | Memory Footprint |
|---|---|---|---|---|---|---|
| SimpleW | 100 | 4.426.408 | 191.138 | 147.546 | 132.374 | 81 Mo |
| FastEndpoints | 90 | 4.015.874 | 189.494 | 133.862 | 121.431 | 47 Mo |
| AspNetCore | 86 | 3.843.972 | 178.713 | 128.132 | 120.090 | 54 Mo |
| GenHttp | 53 | 2.354.276 | 111.569 | 78.475 | 73.196 | 165 Mo |
| FastHttp | 49 | 2.205.770 | 140.447 | 73.525 | 73.324 | ? Mo |
| EmbedIO | 5 | 222.492 | 10.915 | 7.416 | 10.915 | 757 Mo |
SimpleW delivers top performances, Fast-Endpoints is closed but for half of the memory footprint. ASP.NET Core is the 3th.