5 ms·

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.

• bsaul 11y ago
  what were they ?
  • jongalloway2 11y ago
    Netty results are listed on https://github.com/aspnet/benchmarks/ https://github.com/aspnet/benchmarks/ for comparison - latest is 2.8 million requests/s. These are the standard Techempower benchmarks.
• edgyswingset 11y ago
  To be fair, almost everything else has a lot of work to do when compared to netty.
• revelation 11y ago
  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.
  • jongalloway2 11y ago
    This is the TechEmpower plaintext benchmark (http://frameworkbenchmarks.readthedocs.org/en/latest/Project-Information/Framework-Tests/#plaintext 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.
• est 11y ago
  http.sys smokes netty in almost every way.
  • pbz 11y ago
    Doesn't looks like it does: https://github.com/aspnet/benchmarks/blob/dev/README.md https://github.com/aspnet/benchmarks/blob/dev/README.md -- look under experimental baselines
  • bigdubs 11y ago
    it actually doesn't which is kind of shocking on windows because http.sys is kernel mode
• firebones 11y ago
  http ASICs? (Or does that even make sense, given that undiscovered exploits might require a hardware upgrade?)