Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Benchmark #3

Closed
dustinmoris opened this issue Jan 15, 2017 · 7 comments
Closed

Benchmark #3

dustinmoris opened this issue Jan 15, 2017 · 7 comments
Milestone

Comments

@dustinmoris
Copy link
Member

See https://github.com/aspnet/benchmarks

@dustinmoris dustinmoris modified the milestone: Beta Feb 19, 2017
@TheAngryByrd
Copy link
Member

I did add AspNetCore.Lambda to https://github.com/TheAngryByrd/dotnet-web-benchmarks/ . AspNetCore.Lambda was right behind Kestrel Plain!

Disclaimer: These are super simple benchmarks with simple routing and plain text responses.

CPU - Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Operating System - Unix 15.6.0.0 (OSX)
Processor Count - 8
Dotnet Version - 1.0.0-preview2-1-003177
  1. Kestrel Plain at 2,260,301 requests over 30 seconds
  2. AspNetCore.Lambda on Kestrel 2,241,695 requests over 30 seconds
  3. MVC on Kestrel 2,027,391 requests over 30 seconds

Nice!

@dustinmoris
Copy link
Member Author

Nice, thanks for running those!

@dustinmoris
Copy link
Member Author

dustinmoris commented Mar 1, 2017

I had a look at the repo and looks like you have a nice collection of different frameworks there. Did you document the test run and results somewhere publicly so I can reference to it?

@TheAngryByrd
Copy link
Member

Sure ill make a listing soon.

@TheAngryByrd
Copy link
Member

@dustinmoris
Copy link
Member Author

These results look really great. I am glad that Giraffe (formerly known as ASP.NET Core Lambda :)) ranks so high. I would have been surprised if it wouldn't to be honest though, because the additional layer on top of plain kestrel is very thin and especially the app you tested (plain text on a GET request) is doing very little more than plain kestrel...

I wasn't sure how the conversion between C# Tasks and F# Async workflows will be, but from those tests looks like the impact is close to nothing which is great.

Many thanks for running those, I will edit the README in a bit to link to your project and the results.

@dustinmoris
Copy link
Member Author

I have linked it here. Let me know if you would like to change or add something to it.

dustinmoris added a commit that referenced this issue Oct 18, 2018
Let's try again...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants