Erlang Concurrency Model FTW?

While catching up on my reading list, I came across this performance benchmark of C10k web servers.

Implementation	Connection Time (mean)	Latency (mean)	Messages	Connections	Connection Timeouts
Erlang (Cowboy)	865ms	17ms	2849294	10000	0
Haskell (Snap)	168ms	227ms	1187413	4996	108
Java (Webbit)	567ms	835ms	1028390	4637	157
Go	284ms	18503ms	2398180	9775	225
Node.js (websocket)	768ms	42580ms	1170847	5701	4299
Python (ws4py)	1561ms	34889ms	1052996	4792	5208

With the exception of Connection Time, Cowboy totally owns other web servers' asses in all other categories.

In the realm of high concurrency and availability, Erlang still rules supreme.

There are a couple of observations that I want to make:

1. Despite all the hype, Node.js still fails to deliver. Don't get me wrong, I really like the idea of running JavaScript on the server. Most web developers already know JavaScript and can't be bothered to pick up a functional language just to write asynchronous and event-driven software, so the barrier to entry is significantly reduced. I just wish that all the attention and community participation would have resulted in something better in terms of scalability and performance.
2. Although Cowboy's average Connection Time is second worst and eight times Snap's average, practically speaking most users won't even notice the difference as the former still takes less than a second. When it comes to performance, perceived responsiveness matters more than raw numbers. There's a big difference between comparing 100ms to 800ms and 1s to 8s.