Significantly Lower Monitoring HttpExport Memory Footprint (#48854)#48966
Merged
original-brownbear merged 1 commit intoelastic:7.xfrom Nov 12, 2019
original-brownbear:48854-7.x
Merged
Significantly Lower Monitoring HttpExport Memory Footprint (#48854)#48966original-brownbear merged 1 commit intoelastic:7.xfrom original-brownbear:48854-7.x
original-brownbear merged 1 commit intoelastic:7.xfrom
original-brownbear:48854-7.x
Conversation
The `HttpExportBulk` exporter is using a lot more memory than it needs to by allocating buffers for serialization and IO: * Remove copying of all bytes when flushing, instead use the stream wrapper * Remove copying step turning the BAOS into a `byte[]` * This also avoids the allocation of a single huge `byte[]` and instead makes use of the internal paging logic of the `BytesStreamOutput` * Don't allocate a new BAOS for every document, just keep appending to a single BAOS
Collaborator
|
Pinging @elastic/es-core-features (:Core/Features/Monitoring) |
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
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.
The
HttpExportBulkexporter is using a lot more memory than it needs toby allocating buffers for serialization and IO:
byte[]byte[]and instead makes use of the internal paging logic of theBytesStreamOutputbackport of #48854