Do not cache the capture data in database if the capture is from a file#2179
Closed
qining wants to merge 2 commits into
Closed
Do not cache the capture data in database if the capture is from a file#2179qining wants to merge 2 commits into
qining wants to merge 2 commits into
Conversation
Contributor
Author
|
This is to replace #2172 |
This was referenced Sep 4, 2018
Contributor
Author
|
Close as #2186 did the same thing |
This file contains hidden or 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
1 participant
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.
If the capture data is stored in a trace file, do not cache the data in raw bytes again in the database.
This CL reduce memory usage, for a typical application, around 2-4GB.