Track max buffer usage in memory channel statistics#3474
Open
pctablet505 wants to merge 1 commit into
Open
Conversation
Add a max_buffer_used field to MemoryChannelStatistics that reports the largest number of items the channel's buffer has held at once since it was created. This lets users pick a sensible max_buffer_size based on data from a real run instead of guessing. Closes python-trio#1723
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3474 +/- ##
===============================================
Coverage 100.00000% 100.00000%
===============================================
Files 128 128
Lines 19439 19448 +9
Branches 1318 1318
===============================================
+ Hits 19439 19448 +9
🚀 New features to boost your workflow:
|
pctablet505
marked this pull request as ready for review
July 17, 2026 09:40
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.
Adds a
max_buffer_usedfield toMemoryChannelStatistics, tracking the largest number of items the channel's buffer has ever held at once.The use case: when you need buffering but
math.infisn't a reasonablemax_buffer_size, this makes it possible to observe real-world peak usage during a run and pick a sensible limit, instead of guessing.Closes #1723