Optimize MessageCracker.IsHandlerMethod for memory #914
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.
MessageCracker.IsHandlerMethod is calling MethodInfo.GetParameters() method three times leading to minor memory waste. This is because GetParameters() is allocating a new array when method has parameters. If we cache parameters array then we save a bit of memory and make method a bit faster. IL code is also a bit smaller: 119 bytes vs 127.
Unit tests are passing.
Benchmark results:
Benchmark code:
This is obviously a micro optimization since gains (memory and time) are small and unlikely to have any visible effect on application performance. Still I hope you would accept PR.