aspnet

KestrelHttpServer

C#2014–2017

aspnet / KestrelHttpServer · Archived

KestrelHttpServer

[Archived] A cross platform web server for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore

Web Development Systems & Infrastructure

Explore on GitHub Read Hacker News discussions

11Distinct people

14Mentions

0Explicit recommenders

2.6KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

[Archived] A cross platform web server for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

aspnet/benchmarks · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year14 dated mentions

Observed mentions: 2014-11-26 15:20:58 UTC to 2017-12-25 21:39:06 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	3	0	3
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	1	0	1
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	9	2	7
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	1	0	1

What Hacker News says

14 sources

Matthias247·Dec 25, 2017

Regarding HTTP/2: I felt the development of this feature went a little bit "strange". For a long time the feature was blocked by missing support for ALPN negotiation on SSL. There was some interest from the outside to work on it, but discussion on it was stuck for a loooong time (1.5 years). As far as I can see now ALPN support has finally been added to .NET core: https://github.com/dotnet/corefx/pull/24389 HTTP/2 itself requires ALPN to talk to browsers, however a large part of the implementation can already been done without it. Out of personal interest I poured quite a ton of work in the beginning of this year into writing a solid HTTP/2 library for .NET, which could have been the base for webservers as well as things like GRPC: https://github.com/Matthias247/http2dotnet It's state should be good enough to enable HTTP/2 now with less t

Read the rest

han a 2 weeks of work. However unfortunately I never got any feedback around it or felt interest in it, even though I think lots of stakeholders should be aware about it. It seems like the ASP .Net core team is implementing now their own HTTP/2 library, which was far more barebones than mine when I last looked at it (https://github.com/aspnet/KestrelHttpServer/pull/1991). Don't have the time and interest to review the latest state.

In Open Source .NET three years later

skun·Nov 25, 2016

Full disclosure: We [0] have been a .NET/Windows house since the product was launched 8 years ago. When RC1 of .NET core was announced, we jumped on it (in spite of all the limitations that it came with) and haven't been disappointed. We've been working on a product whose pilot version handled to the tune of 40K requests in a day on a 1GB/1Core Linode box --- As far as choice of platform goes, it all comes down to a few factors for me 1. What the team is comfortable with: This is *crucial* and in retrospect it is the biggest contributing factor that helped us take our next product to production -- fast. If you have a team that is comfortable with .NET then just go for it. Everything else can be figured out later. 2. What the ecosystem is like: If you have a fair idea of what you're building out, scout the ecosystem

Read the rest

and see if it offers everything that you need. We more or less found everything that we needed except a good Excel wrangling library. --- Also I feel the .NET core VS Node question is skewed because comparatively, Node is a platform that has been around for much longer and has much bigger adoption. Keeping this in mind, there will definitely be problems with .NET Core. Eg: If you're looking to reference a class library that is running with the full framework then you'll be hitting a few hurdles and stoppers. The good part however is that it is constantly under work and we're able to actually see the performance improvements. [1][2] The bad part however is that it is constantly under work so expect flux. [3][4] --- Experience wise, its been great working with .NET Core. Projects like VS Code make it a breeze. To me, C# has always been a well architected, beautiful language and now I'm able to write it in the way I want to -- without using a bloated IDE like Visual Studio and run it where I want to -- On cheap linux boxes without worrying about licensing costing. For us at Logic Soft, .NET core really was a lifesaver when our next logical transition was the web and we were a .NET house shipping software on windows :) Footnotes: [0]: http://logicsoft.co.in [1]: https://www.techempower.com/blog/2016/11/16/framework-benchm... [2]: https://github.com/aspnet/KestrelHttpServer/pull/1138 [3]: https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-t... [4]: http://ivanz.com/2016/05/17/farewell-project-json-hello-msbu...

In Ask HN: Node vs. .NET Core

philliphaydon·Nov 22, 2016Submission

KestrelHttpServer SuperCharged MemoryPoolIterator

95 points · Open discussion

halter73·Nov 16, 2016

In the long term yes. When we switch to System.Net.Sockets it will be done with an emphasis on transport agnosticism. [1] ATM, it looks like Sockets will be the priority since it's a cross platform API more similar to what libuv currently provides. [1] https://github.com/aspnet/KestrelHttpServer/issues/828

In Announcing .NET Core 1.1

skyde·Nov 16, 2016

Could someone explain why "ASP.NET Core 1.1" Kestrel webserver decided to use LibUV DllImpor [1] instead of .NET Asynchronous Server Socket (System.Net.Sockets) [2]. Does that mean that the managed implementation of Async socket is broken and was too slow? [1] "https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic.... [2] https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110).....

In Announcing .NET Core 1.1

skyde·Nov 16, 2016

Could someone explain why "ASP.NET Core 1.1" Kestrel webserver decided to use LibUV DllImpor [1] instead of .NET Asynchronous Server Socket (System.Net.Sockets) [2]. Does that mean that the managed implementation of Async socket is broken and was too slow? [1] "https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic... [2] https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110)....

In Announcing the Fastest ASP.NET Yet, ASP.NET Core 1.1 RTM

Nelkins·Oct 3, 2016Submission

Ben's Magic Number

1 points · Open discussion

cesarbs·May 4, 2016

On a related note, we go through great lengths in the Kestrel HTTP server [0] (which also uses libuv) to have fast HTTP parsing. As an example, we attempt to read the method and the HTTP version as longs and compare them to pre-computed longs in order to have fast comparisons and reuse strings containing standard methods and versions (reducing memory allocation is the main driver of our optimizations) [1], so we don't have to allocate those strings on every request. We do a similar thing for headers [2]. We also manage a lot of our own memory, despite using a garbage collected language [3]. [0] https://github.com/aspnet/KestrelHttpServer [1] https://github.com/aspnet/KestrelHttpServer/blob/3a424f6abac... [2] https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic... [3] https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic...

In Uvloop: Fast Python networking

jongalloway2·Feb 18, 2016

Update: Checked with the team, latest Linux benchmark for plaintext with pipelining from January was 928,023 rps, which is a lot closer to the Windows numbers (78%). Updated here: https://github.com/aspnet/benchmarks/#plain-text-with-http-p... Linux benchmarks are included here: https://github.com/aspnet/benchmarks/ The team definitely wants to make ASP.NET Core run fast on Linux, too. The ASP.NET team perf rig runs both Ubuntu 14.04 LTS and Windows Server 2012 R2. A lot of the perf enhancements are due to community pull requests, mostly from Ben (author of parent post). The perf work's been discussed a lot on the weekly community standup calls (http://live.asp.net), here's one going over the rig and perf in general: https://www.youtube.com/watch?v=7O81CAjmOXk&list=PL0M0zPgJ3H... There's a lot going on right now - both ASP.NET Core and .N

Read the rest

ET Core are new to Linux, the teams are working on getting 1.0 releases out the door, etc. I expect perf on both Windows and Linux to continue to improve, both before and after 1.0 release. This week on the community standup, Damian said that perf is one area that's lower risk as RTM approaches, and that they're hoping for more improvement there. And this is very much an open source project, as you can see from the merged pull requests in general (https://github.com/aspnet/KestrelHttpServer/pulls?q=is%3Apr+...) and the fact that Ben (non m-dollar) is battling with a Microsoft dev to be the top contributor. It'd be great to get some more devs with Linux HTTP serving background contributing. I think I remember that they only posted benchmark updates when there was a significant change. Checking with the team now. Source: long time ASP.NET groupie, Microsoft employee (until they find out I'm goofing off on HN instead of replying to e-mail).

In ASP.NET Core – 2300% More Requests Served per Second

benaadams·Jan 20, 2016

(Author of article) Working on it, currently the #1 contributor to AspNet Core's new webserver, and it is doing about 2.5M rps on equivalent techempower hardware https://github.com/aspnet/KestrelHttpServer/graphs/contribut...

In Serving 6.8M requests per second at 9 Gbps from a single Azure VM

jongalloway2·Nov 18, 2015

It's confusing, but ASP.NET 5 ships with ASP.NET MVC 6. ASP.NET MVC 5 was released in October, 2013. I'm assuming you meant ASP.NET 5 / ASP.NET MVC 6 since that's what was announced today. There's a good chance you know this, but since some people reading this thread might not I figured I'd give some more detail. It's definitely in Microsoft's interest to make Azure a great place to host your ASP.NET applications. The team that builds ASP.NET is part of the Azure group, and that's what pays the bills. (disclaimer: Microsoft employee, Azure fan) However, ASP.NET 5 has been built to run great on your own web server. In addition to IIS on Windows, ASP.NET 5 has a cross platform, open source web server named Kestrel that runs on Windows, Mac and Linux: https://github.com/aspnet/KestrelHttpServer/ The team's working really hard to make sure th

Read the rest

at ASP.NET 5 not only runs cross platform, but that it works well and runs really fast cross-platform: https://github.com/aspnet/benchmarks/blob/master/README.md

In Announcing .NET Core and ASP.NET 5 RC

bigdubs·Dec 30, 2014

https://github.com/aspnet/KestrelHttpServer don't need to wait much longer; it's already faster than nodejs for trivial benchmarks and getting better every day.

In Under the Hood with Java 10 Enhanced Generics

SideburnsOfDoom·Dec 6, 2014

I saw some talks on ASP.Net vNext this week and the links between .Net web apps and IIS are weaker than ever. I'm sure that .Net web apps will still be deployed to IIS when they need to scale a lot, and are hosted on windows, but neither of those two are mandatory any more. A lot of sites and web services won't need all that and can use a self-host or lightweight host. OR new hosts/adapters to other web servers can be written. There's a lot more hosting and platform flexibility coming, which is exciting. For more info, see http://www.asp.net/vnext/overview/aspnet-vnext/aspnet-5-over... http://www.asp.net/aspnet/overview/owin-and-katana/getting-s... https://github.com/aspnet/KestrelHttpServer

In Introducing .NET Core

bigdubs·Nov 26, 2014

The Kestrel (https://github.com/aspnet/KestrelHttpServer) web server that is included in ASP.net vNext uses Libuv at it's core. Pretty cool that this project is becoming more mature.

In Moving the joyent/libuv repository to libuv/libuv