Hacker News Reader

Comment by bigdubs | Hacker News Reader

I remember reading these results a little while ago and thought the numbers were great until I saw the netty results. There is a lot of work left to be done.

View on HN

To be fair, almost everything else has a lot of work to do when compared to netty.

Screams micro-benchmark when you can saturate a 10Gb with the server quite readily. If you can't, chances are the problem is somewhere else anyway.

This is the TechEmpower plaintext benchmark (http://frameworkbenchmarks.readthedocs.org/en/latest/Project...). I'd agree that it's kind of a micro-benchmark. There are other TE benchmarks that test more real-world web application scenarios.

My understanding is that the ASP.NET team started at the bottom of the stack and is working their way up. They want to get fundamental HTTP serving basics nailed first. I think that makes sense - they were getting around 170k rps in September, so there were definitely some things to sort out at the basic HTTP serving layer.

http.sys smokes netty in almost every way.

Doesn't looks like it does: https://github.com/aspnet/benchmarks/blob/dev/README.md -- look under experimental baselines

it actually doesn't which is kind of shocking on windows because http.sys is kernel mode

http ASICs?

(Or does that even make sense, given that undiscovered exploits might require a hardware upgrade?)

what were they ?

Netty results are listed on https://github.com/aspnet/benchmarks/ for comparison - latest is 2.8 million requests/s. These are the standard Techempower benchmarks.

Reply on news.ycombinator.com