Remove inefficient Regexp scan in compress_snappy_stream #44
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
Contrary to our expectation, we observed that logstash process consumes more CPU time when using Snappy compression than when using GZ. Profiling shows that the Regexp scans for splitting the input data into chunks were using a large portion of the CPU time. We can change it to a simple substring loop and remove the unnecessary overhead.
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.
Contrary to our expectation, we observed that logstash process consumes more CPU time when using Snappy compression than when using gzip.
Profiling shows that the Regexp scans for splitting the input data into chunks were using a large portion of the CPU time.
We can change it to a simple substring loop and remove the unnecessary overhead.