feat: libaustin #136
Draft
feat: libaustin #136
Conversation
This file contains 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
P403n1x87
force-pushed
the
libaustin
branch
2 times, most recently
from
5b7b1e2
to
68133de
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## devel #136 +/- ##
==========================================
- Coverage 71.49% 69.00% -2.49%
==========================================
Files 25 25
Lines 2473 2568 +95
Branches 730 733 +3
==========================================
+ Hits 1768 1772 +4
- Misses 381 461 +80
- Partials 324 335 +11
☔ View full report in Codecov by Sentry. |
This change improves the report from benchmark runs by adding t-tests for each scenario. This allows the benchmarks to provide a summary at the end with the scenarios that are likely to show perfomance difference between the latest released version and the one that comes with the PR the benchmarks run for. This also updates the versions that are being benchmarked to include the latest releases.
ci(benchmarks): improve benchmark reporting
This change adds a data validation workflow. Data is validated by performing a Hotelling T2 test on the collected data.
ci: add data validation workflow
This change adds extra steps to the CI workflows to build Python wheels so that the Austin binary can be installed with pip from PyPI.
ci: build Python wheels
Unused variable alloc
The d_name variable is a table of 256. It can not be null.
P403n1x87
force-pushed
the
libaustin
branch
8 times, most recently
from
159584a
to
4704f2f
Compare
Austin BenchmarksRunning Austin benchmarks with Python 3.10.11 Wall 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]
Benchmark SummaryComparison of dev against 3.5.0. The following scenarios show a statistically significant difference in performance between the two versions.
|
P403n1x87
force-pushed
the
libaustin
branch
5 times, most recently
from
33f27b5
to
17e7249
Compare
P403n1x87
force-pushed
the
libaustin
branch
2 times, most recently
from
5e45ba6
to
403d2e6
Compare
Use the more correct expression for computing the lasti index with Python 3.11.
ci(ubuntu): update before install
The version of cppcheck available from the package manager tends to be outdated. In this change we build from sources instead. We cache the build result for faster execution.
chore: minor compilation fixes with gcc 11.3
ci(checks): build cppcheck from sources
refactor: use proper lasti formula for 3.11
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.
Requirements for Adding, Changing, Fixing or Removing a Feature
Fill out the template below. Any pull request that does not include enough
information to be reviewed in a timely manner may be closed at the maintainers'
discretion.
Description of the Change
Alternate Designs
Regressions
Verification Process