Open
Conversation
…he most common end user scenario
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Disclaimer: I don't expect this PR to get merged, I just want to share updated perf numbers to start a discussion.
Empty: an empty console app that prints a boolean and string to the output
EmpyAOT - same app compiled with CoreRT (I've used the 6.0 bits of
Microsoft.DotNet.ILCompiler)Corefxlab - app that uses corefxlab parser (I had to copy-paste the code as the nuget package is not available anymore) to parse a boolean and a string
SystemCommandLineBefore - app that uses System.CommandLine before all recent perf work (PRs)
SystemCommandLineAfter - app that uses System.CommandLine with all recent perf improvements
SystemCommandLineAfterR2R - same as above, but published with
PublishReadyToRun=trueSystemCommandLineAfterAOT - same as above, but compiled to native library (possible due to all the @jonsequitur recent work)
The initial gap with coreflab parser was 25ms for given scenario. We were able to reduce this gap by 20ms.