It would be much more interesting to see benchmarks that evaluate
response latency or maximum number of concurrent connections. Or a
combination of both. That's where Erlang will really shine.
Requests/s is boring (and absolutely doesn't mean one server is faster
than another!), especially with keep-alive. As I mentioned in my talk in
SF, requests/s benchmarks weren't able to show any performance increase
in recent Cowboy versions, despite production nodes being able to handle
2 times more traffic than older versions.
--
Loïc Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu
_______________________________________________
erlang-questions mailing list
erlang-q...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions