chore: event buffering in pipe mode #319
Merged
Conversation
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
When in pipe mode we do event buffering. This is the equivalent of line buffering but for the two main Austin events, that is samples and metadata. With this change, any tool communicating with Austin via a pipe will get the bytes for each event immediately instead of at the default stream buffer size. This allows tools to get events from Austin in real-time as they are collected instead of periodic bursts.
Austin Data ValidationPython 3.9✨ All scenarios validated successfully! ✨ Python 3.10✨ All scenarios validated successfully! ✨ Python 3.11✨ All scenarios validated successfully! ✨ Python 3.12✨ All scenarios validated successfully! ✨ Python 3.13✨ All scenarios validated successfully! ✨ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## devel #319 +/- ##
========================================
Coverage ? 67.59%
========================================
Files ? 32
Lines ? 2756
Branches ? 792
========================================
Hits ? 1863
Misses ? 507
Partials ? 386 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Austin BenchmarksRunning Austin benchmarks with Python 3.13.7 Benchmark SummaryComparison of dev against base. The following scenarios show a statistically significant difference in performance between the two versions.
Benchmark ResultsWall time [sampling interval: 1]Wall time [sampling interval: 1]
Wall time [sampling interval: 10]Wall time [sampling interval: 10]
Wall time [sampling interval: 100]Wall time [sampling interval: 100]
Wall time [sampling interval: 1000]Wall time [sampling interval: 1000]
CPU time [sampling interval: 1]CPU time [sampling interval: 1]
CPU time [sampling interval: 10]CPU time [sampling interval: 10]
CPU time [sampling interval: 100]CPU time [sampling interval: 100]
CPU time [sampling interval: 1000]CPU time [sampling interval: 1000]
RSA keygen [sampling interval: 1]RSA keygen [sampling interval: 1]
RSA keygen [sampling interval: 10]RSA keygen [sampling interval: 10]
RSA keygen [sampling interval: 100]RSA keygen [sampling interval: 100]
RSA keygen [sampling interval: 1000]RSA keygen [sampling interval: 1000]
Full metrics [sampling interval: 1]Full metrics [sampling interval: 1]
Full metrics [sampling interval: 10]Full metrics [sampling interval: 10]
Full metrics [sampling interval: 100]Full metrics [sampling interval: 100]
Full metrics [sampling interval: 1000]Full metrics [sampling interval: 1000]
Multiprocess wall time [sampling interval: 1]Multiprocess wall time [sampling interval: 1]
Multiprocess wall time [sampling interval: 10]Multiprocess wall time [sampling interval: 10]
Multiprocess wall time [sampling interval: 100]Multiprocess wall time [sampling interval: 100]
Multiprocess wall time [sampling interval: 1000]Multiprocess wall time [sampling interval: 1000]
|
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.
When in pipe mode we do event buffering. This is the equivalent of line buffering but for the two main Austin events, that is samples and metadata. With this change, any tool communicating with Austin via a pipe will get the bytes for each event immediately instead of at the default stream buffer size. This allows tools to get events from Austin in real-time as they are collected instead of periodic bursts.
Note
This change has a performance impact on pipe mode.