Conversation
Owner
|
Nice, thank you! Did you test that the memory consumption is lower by using I'm still testing it with and without to compare the memory consumption of both variants. |
Contributor
Author
|
@eht16 , yes, here is 2 graphics, 1 one is Queue, second one - PriorityQueue |
8 tasks
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.


We faced with steady increasing of RAM consumption in AWS ECS and this began to happen after adding python-logstash-async library.
There is a known issue about Queue memory leak: https://bugs.python.org/issue43911
The simplest way to get rid of it - change Queue to PriorityQueue