Keep event history in circular buffer #316
Merged
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.
Event history stored in circular buffer
Description, Motivation and Context
Storing event history in a circular buffer avoids memory allocation after the storage limit is reached.
What is the current behavior?
When event history limit is reached, the beginning of the history entries slice is ignored:
entries = entries[1:]
What is the new behavior?
A circular buffer is used instead to store event history.
What kind of change does this PR introduce?
Checklist: