CodSpeedHQ
valgrind-codspeed
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
refactor(bench): migrate benchmarks to codspeed exec CLI
#16
Merged
Comparing
cod-2766-migrate-valgrind-benchmarks-to-exec-cli
(
d2dd609
) with
master
(
4a64bb2
)
CodSpeed Performance Gauge
N/A
New
60
Skipped
60
Benchmarks
Mode
CPU Simulation
Wall Time
Memory
Status
New
Skipped
120 total
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
N/A
N/A
6.8 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
N/A
N/A
5.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, no-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
2.5 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
N/A
N/A
4.3 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
N/A
N/A
7.7 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, echo Hello, World!, no-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
496.5 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, stress-ng --cpu 1 --cpu-ops 10, inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
4.5 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
N/A
N/A
5.3 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
N/A
N/A
4.5 s
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
N/A
N/A
729.7 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, inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
7.2 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-no-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
3 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
N/A
N/A
663.9 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind-3.25.1, python3 testdata/test.py, full-with-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
6.9 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-no-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
8.3 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
N/A
N/A
563.1 ms
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
N/A
N/A
8.5 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, no-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
3.1 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, inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
3.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, no-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
4.1 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
N/A
N/A
3.5 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
N/A
N/A
6.8 s
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, testdata/take_strings-aarch64 varbinview_non_null, full-no-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
3.1 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
N/A
N/A
567.8 ms
Uses the
Wall Time instrument
to collect wall time performance metrics.
test_valgrind[valgrind.codspeed, testdata/take_strings-aarch64 varbinview_non_null, full-with-inline]
exec_harness
CodSpeed Performance Gauge
N/A
N/A
7.2 s
1
2
3
4
5
Commits
Click on a commit to change the comparison range
No baseline data is yet available
Once your main branch has generated a first performance report, you will see the list of commits and their performance impact here.
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs