CodSpeedHQ
valgrind-codspeed
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
fix(callgrind): initialize stack on instrumentation start
#15
Merged
Comparing
cod-2714-investigate-pytest-flamegraph-regression-final
(
ae9ee5c
) with
master
(
d2dd609
)
CodSpeed Performance Gauge
-73%
Improvement
2
Regression
1
Untouched
37
Skipped
80
Benchmarks
Mode
CPU Simulation
Wall Time
Memory
Status
Regression
Improvement
Untouched
Skipped
120 total
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, echo Hello, World!, full-with-inline]
exec_harness
CodSpeed Performance Gauge
-99%
733.6 ms
51,937.6 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, python3 testdata/test.py, full-with-inline]
exec_harness
CodSpeed Performance Gauge
+25%
8.7 s
7 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, python3 testdata/test.py, full-no-inline]
exec_harness
CodSpeed Performance Gauge
+11%
7.5 s
6.8 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, stress-ng --cpu 1 --cpu-ops 10, no-inline]
exec_harness
CodSpeed Performance Gauge
+6%
4.3 s
4.1 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, python3 testdata/test.py, full-no-inline]
exec_harness
CodSpeed Performance Gauge
+5%
7.2 s
6.8 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, stress-ng --cpu 1 --cpu-ops 10, full-no-inline]
exec_harness
CodSpeed Performance Gauge
+3%
8.4 s
8.2 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, stress-ng --cpu 4 --cpu-ops 10, full-no-inline]
exec_harness
CodSpeed Performance Gauge
+1%
5.5 s
5.4 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, stress-ng --cpu 4 --cpu-ops 10, full-no-inline]
exec_harness
CodSpeed Performance Gauge
+1%
5.4 s
5.3 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, stress-ng --cpu 1 --cpu-ops 10, full-with-inline]
exec_harness
CodSpeed Performance Gauge
+1%
8.2 s
8.1 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, stress-ng --cpu 4 --cpu-ops 10, no-inline]
exec_harness
CodSpeed Performance Gauge
+1%
3.2 s
3.1 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, stress-ng --cpu 1 --cpu-ops 10, no-inline]
exec_harness
CodSpeed Performance Gauge
+1%
4.2 s
4.2 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, stress-ng --cpu 4 --cpu-ops 10, inline]
exec_harness
CodSpeed Performance Gauge
+1%
3.4 s
3.4 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, python3 testdata/test.py, inline]
exec_harness
CodSpeed Performance Gauge
+1%
4.5 s
4.5 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, testdata/take_strings-aarch64 varbinview_non_null, full-with-inline]
exec_harness
CodSpeed Performance Gauge
0%
7.8 s
7.8 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, python3 testdata/test.py, no-inline]
exec_harness
CodSpeed Performance Gauge
0%
4.3 s
4.3 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, echo Hello, World!, no-inline]
exec_harness
CodSpeed Performance Gauge
0%
501 ms
499.8 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, stress-ng --cpu 4 --cpu-ops 10, inline]
exec_harness
CodSpeed Performance Gauge
0%
3.3 s
3.2 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, echo Hello, World!, inline]
exec_harness
CodSpeed Performance Gauge
0%
695.5 ms
694.7 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, stress-ng --cpu 4 --cpu-ops 10, full-with-inline]
exec_harness
CodSpeed Performance Gauge
0%
5.6 s
5.6 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, echo Hello, World!, full-no-inline]
exec_harness
CodSpeed Performance Gauge
0%
566 ms
566.7 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, python3 testdata/test.py, inline]
exec_harness
CodSpeed Performance Gauge
0%
4.6 s
4.6 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, stress-ng --cpu 4 --cpu-ops 10, full-with-inline]
exec_harness
CodSpeed Performance Gauge
0%
5.5 s
5.5 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, echo Hello, World!, inline]
exec_harness
CodSpeed Performance Gauge
0%
663.8 ms
664.9 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, testdata/take_strings-aarch64 varbinview_non_null, no-inline]
exec_harness
CodSpeed Performance Gauge
0%
2.5 s
2.5 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, echo Hello, World!, full-no-inline]
exec_harness
CodSpeed Performance Gauge
0%
562.4 ms
563.5 ms
1
2
3
4
5
Commits
Click on a commit to change the comparison range
Base
master
d2dd609
-73.05%
test(callgrind): add regression tests for runtime obj-skip
ae9ee5c
6 days ago
by not-matthias
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs