Measure the per request split between GraphQL.NET, the library and EF - #1405
Merged
Conversation
Benchmarks that isolate the stages of a request: GraphQL.NET alone for the same result shape, the full request, the argument and projection trees the library builds, and EF executing the projected query, on InMemory and on LocalDB. The trees are 0.2% of a request, so a per shape cache of the projection has nothing to recover; the numbers and the source generator assessment are recorded in todo.md. The Benchmarks assembly is signed so the library can expose its internals to the stage benchmarks. Each setup uses its own InMemory database name, since GlobalSetup runs once per method and a shared name seeds on top of the previous data.
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
1 participant
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.
Benchmarks that isolate the stages of a request: GraphQL.NET alone for the same result shape, the full request, the argument and projection trees the library builds, and EF executing the projected query, on InMemory and on LocalDB. The trees are 0.2% of a request, so a per shape cache of the projection has nothing to recover; the numbers and the source generator assessment are recorded in todo.md.
The Benchmarks assembly is signed so the library can expose its internals to the stage benchmarks. Each setup uses its own InMemory database name, since GlobalSetup runs once per method and a shared name seeds on top of the previous data.