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

Faster dotnetcore, add parallel, better timing #40

Merged
merged 3 commits into from
Aug 1, 2016

Conversation

benaadams
Copy link
Contributor

Added Parallel, Single threaded Async; multithreaded Async and ValueTask Async

If you use the Release config

dotnet run --configuration Release

or compile it in release mode...

dotnet compile --configuration Release -o bin
bin\dnx

The results are (Win10 on iMac Intel i5 @ 2.9GHz)

Arch 64 bit - Cores 4
499999500000
1 Thread - Sync: 5.756ms
499999500000
1 Thread - Async: 146.579ms
499999500000
1 Thread - ValueTask Async: 16.917ms
499999500000
Parallel Async: 86.191ms
499999500000
Parallel - ValueTask Async: 4.988ms
499999500000
Parallel Sync: 1.661ms

Debug mode matches the current results

Arch 64 bit - Cores 4
499999500000
1 Thread - Sync: 42.653ms
499999500000
1 Thread - Async: 186.333ms
499999500000
1 Thread - ValueTask Async: 64.792ms
499999500000
Parallel Async: 84.977ms
499999500000
Parallel - ValueTask Async: 19.903ms
499999500000
Parallel Sync: 13.490ms

@benaadams benaadams force-pushed the parallel+timing branch 4 times, most recently from ede1673 to 5afaa0e Compare February 15, 2016 12:12
@benaadams benaadams force-pushed the parallel+timing branch 2 times, most recently from 6e4193f to eac1cc0 Compare February 15, 2016 13:16
@benaadams benaadams changed the title dotnetcore add parallel, better timing Faster dotnetcore, add parallel, better timing Feb 15, 2016
@Jetski5822
Copy link

whoah, didn't realize what ValueTask Async gave us! +1

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

Successfully merging this pull request may close these issues.

3 participants