Change from radix/v4 to go-redis due to high lock overhead on EncodeDecode. Current best performance vs all previous versions #14
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.
EncodeDecode now acquires a lock on radix/v4 which can represent a large overhead in scenarios of high load.
To avoid having radix/v4 impact this benchmark tool we're moving to the go-redis client ( with the change of redis/go-redis#2570 )
Results of v0.0.6 ( radix/v3 ) -- -- Message Rate 796851
Results of v0.0.7 forward ( radix/v4 ) -- Message Rate 295370
Results of this branch ( go-redis ) -- Message Rate 865977