Update runtime versions and optimise dotnet implementation #3
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.
Update dotnet to version 3.1 and Go to version 1.14.3.
Avoid intermediate objects while serializing and deserializing to reduce the heap allocations, and use struct instead of class in the dotnet implementation.
While I was doing the stress test after the optimization I noticed that most of the time was taking generating the message for the
/data
endpoint, because of this I changed the logic to serialize just one time to have some dummy data.Benchmarks results:
Dotnet before the changes
Golang before the changes
Dotnet after the changes
Golang after the changes