Only use the token queue for fields we really can't parse immediately#628
Merged
slinkydeveloper merged 3 commits intocloudevents:masterfrom Nov 26, 2020
Merged
Conversation
Signed-off-by: Markus Thömmes <markusthoemmes@me.com>
Member
slinkydeveloper
left a comment
There was a problem hiding this comment.
Can you run with count=5 and benchtime=5s? I would love to check if the time difference is simple noise over the different runs
Signed-off-by: Markus Thömmes <markusthoemmes@me.com>
slinkydeveloper
approved these changes
Nov 26, 2020
1 task
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.
Most of the keys are parsed identically between the versions, so why bother deferring their parsing and allocating stuff unnecessarily? This also puts an upper bound on the tokenQueue in theory.
Signed-off-by: Markus Thömmes markusthoemmes@me.com
Benchmark