Measuring response times (routing times) for each framework (middleware). Each framework has to have two features; routing and parsing path parameters.

Last update: 2018-01-18

OS: Darwin (version: 17.3.0, arch: x86_64)
CPU Cores: 8

1. iron (rust)
2. router_cr (crystal)
3. nickel (rust)
4. raze (crystal)
5. japronto (python)
6. fasthttprouter (go)
7. kemal (crystal)
8. rocket (rust)
9. iris (go)
10. echo (go)
11. aspnetcore (csharp)
12. gorilla_mux (go)
13. plug (elixir)
14. gin (go)
15. phoenix (elixir)
16. vapor (swift)
17. perfect (swift)
18. sanic (python)
19. kitura (swift)
20. clusterexpress (node)
21. akkahttp (scala)
22. express (node)
23. roda (ruby)
24. jester (nim)
25. criollo (objc)
26. sinatra (ruby)
27. rails (ruby)

1. rust (iron)
2. crystal (router_cr)
3. python (japronto)
4. go (fasthttprouter)
5. csharp (aspnetcore)
6. elixir (plug)
7. swift (vapor)
8. node (clusterexpress)
9. scala (akkahttp)
10. ruby (roda)
11. nim (jester)
12. objc (criollo)

• Ruby
  • Rails
  • Sinatra
  • Roda
• Crystal
  • Kemal
  • raze
  • router.cr
• Go
  • Echo
  • gorilla-mux
  • iris
  • fasthttprouter
  • Gin
• Rust
  • IRON
  • nickel.rs
  • Rocket (nightly)
• node
  • express
  • express/cluster
• Elixir
  • Plug
  • Phoenix
• Swift
  • Vapor
  • Perfect
  • Kitura
• Scala
  • Akka-Http (Routing DSL)
• C#
  • ASP.NET Core
• Python
  • sanic
  • japronto
  • flask
• Nim
  • Jester
• Objective-C
  • Criollo

See Development section when you want to add new languages or frameworks.

We want to know the response time (routing time), not a usability. So full-stack framework is at a disadvantage.

• Each server has no special logics.
• Each server's executable is named as server_[Lauguage]_[Framework]. (For example, server_ruby_sinatra)
• There are only 3 routes
  • GET '/' return status code 200 with empty body
  • GET '/user/:id' return status code 200 with the id
  • POST '/user' return status code 200 with empty body

Required environment -> See Current target frameworks(middlewares)

Neph is a modern command line job processor that can be substitute for make command.

To compile servers and benchmarker,

> neph

For each language,

> neph ruby

For each framework,

> neph rails

See neph.yaml

To compile servers and benchmarker,

> make

For each language,

> make ruby

For each framework,

> make rails

You can take a benchmark by

> bin/benchmarker

For each language

> bin/benchmarker ruby

For each framework

> bin/benchmarker rails

For comparison (Comparing rails, kemal and router.cr in this example)

> bin/benchmarker rails crystal

If you take it manually, you can run each server by

> bin/server_[Language]_[Framework]

and run client by

> time bin/client

You can set # of threads and # of the loops of the request(there are 3 requests in a loop) by

> time bin/client -t 16 -r 1000

In the above example, 16 threads requests 1000 * 3 times. So 48000 requests are sent in total.

Setup servers by using docker is under WIP. Currently, crystal and ruby servers are supported. For example

docker-compose up rails

Then you can run your client by

time ./bin/client

• Give me PR when you want to add other web frameworks
• Give me PR when you can tuning each framework (under the rule)

• /[language]/[framework]/[codes] <- Project itself
• benchmarker/benchmarker.cr <- Adding it as a target to
• README.md <- Adding it as a target framework of the list
• Makefile
• neph.yaml (optional)

Anyway, you don't have to care about details since maintainer can fix them after merging it. The result will be updated by maintainer.

1. Fork it (https://github.com/tbrand/which_is_the_fastest/fork)
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

• tbrand Taichiro Suzuki - creator, maintainer
• OvermindDL1 OvermindDL1 - maintainer

1AE9P6TUVik1rJGQhaSqGWRk1oAQ3DJnmo