[WIP] Akka.Serializer performance fixes #3532
Open
Conversation
This file contains 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.
Noticed some unnecessary allocations inside the
Serializerclass while I was doing some other work today (working on an Akka.Persistence) plugin. Redesigned those portions to prevent garbage collection.This code affects not just Akka.Remote, but also the Akka.Persistence and any other serializer that might need to serialize an
IActorRef.When I ran the RemotePingPong numbers I didn't see a significant material difference - not sure why yet.
WIP-ing this because I want to see some of the build server numbers and because I think it may be worth benchmarking this specific method independently from the entire Akka.Remote messaging pipeline.