Comparing
cod-2766-migrate-valgrind-benchmarks-to-exec-cli
(d2dd609
) withmaster
(4a64bb2
)N/A
- New
- 60
- Skipped
- 60
Benchmarks
60 total
The benchmarks below were skipped, so their baseline results are used instead. If they were deleted in your codebase, archive them to remove them from the performance reports.
Learn more about archiving benchmarks
Learn more about archiving benchmarks
test_valgrind[valgrind.codspeed, testdata/take_strings-aarch64 varbinview_non_null, no-inline]
bench/bench.pySkipped
2.5 s*
test_valgrind[valgrind.codspeed, testdata/take_strings-aarch64 varbinview_non_null, full-no-inline]
bench/bench.pySkipped
3.1 s*
test_valgrind[valgrind.codspeed, testdata/take_strings-aarch64 varbinview_non_null, inline]
bench/bench.pySkipped
6.8 s*
test_valgrind[valgrind.codspeed, testdata/take_strings-aarch64 varbinview_non_null, full-with-inline]
bench/bench.pySkipped
7.4 s*
test_valgrind[valgrind-3.25.1, echo Hello, World!, full-with-inline]
bench/bench.pySkipped
749.6 ms*
test_valgrind[valgrind.codspeed, echo Hello, World!, inline]
bench/bench.pySkipped
714.1 ms*
test_valgrind[valgrind-3.25.1, echo Hello, World!, no-inline]
bench/bench.pySkipped
508.4 ms*
test_valgrind[valgrind-3.25.1, stress-ng --cpu 1 --cpu-ops 10, full-no-inline]
bench/bench.pySkipped
8.2 s*
test_valgrind[valgrind-3.25.1, python3 testdata/test.py, inline]
bench/bench.pySkipped
3.9 s*
test_valgrind[valgrind.codspeed, echo Hello, World!, no-inline]
bench/bench.pySkipped
513 ms*
test_valgrind[valgrind-3.25.1, echo Hello, World!, full-no-inline]
bench/bench.pySkipped
578.2 ms*
test_valgrind[valgrind-3.25.1, stress-ng --cpu 1 --cpu-ops 10, inline]
bench/bench.pySkipped
4.5 s*
test_valgrind[valgrind.codspeed, echo Hello, World!, full-no-inline]
bench/bench.pySkipped
578.6 ms*
test_valgrind[valgrind.codspeed, python3 testdata/test.py, full-no-inline]
bench/bench.pySkipped
5.6 s*
test_valgrind[valgrind-3.25.1, stress-ng --cpu 1 --cpu-ops 10, full-with-inline]
bench/bench.pySkipped
8.2 s*
test_valgrind[valgrind.codspeed, python3 testdata/test.py, inline]
bench/bench.pySkipped
3.9 s*
test_valgrind[valgrind-3.25.1, python3 testdata/test.py, no-inline]
bench/bench.pySkipped
3.7 s*
test_valgrind[valgrind-3.26.0, stress-ng --cpu 1 --cpu-ops 10, full-with-inline]
bench/bench.pySkipped
8.5 s*
test_valgrind[valgrind.codspeed, python3 testdata/test.py, full-with-inline]
bench/bench.pySkipped
5.7 s*
test_valgrind[valgrind-3.25.1, stress-ng --cpu 1 --cpu-ops 10, no-inline]
bench/bench.pySkipped
4.4 s*
test_valgrind[valgrind-3.25.1, python3 testdata/test.py, full-no-inline]
bench/bench.pySkipped
6 s*
test_valgrind[valgrind-3.26.0, stress-ng --cpu 1 --cpu-ops 10, full-no-inline]
bench/bench.pySkipped
8.2 s*
test_valgrind[valgrind-3.26.0, echo Hello, World!, full-no-inline]
bench/bench.pySkipped
581.7 ms*
test_valgrind[valgrind-3.26.0, stress-ng --cpu 1 --cpu-ops 10, inline]
bench/bench.pySkipped
4.5 s*
test_valgrind[valgrind.codspeed, python3 testdata/test.py, no-inline]
bench/bench.pySkipped
4.4 s*
Commits
Click on a commit to change the comparison rangeNo baseline data is yet availableOnce your main branch has generated a first performance report, you will see the list of commits and their performance impact here.