CodSpeedHQ
codspeed-node
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
chore(tinybench): emit benchmark markers
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
3 hours ago
chore(tinybench): emit benchmark markers
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
3 hours ago
chore(tinybench): emit benchmark markers
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
4 hours ago
fix(ci): only run the macOS-only bench on the macOS walltime job Pass the vitest file filter through turbo so the macOS job runs just macos.bench.ts. The full vitest-plugin suite already runs on the linux walltime job, and uploading the same benchmark twice for one commit fails CodSpeed processing ("Found the same benchmark multiple times"). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
4 hours ago
fix(tinybench): emit a single walltime marker pair per bench run Move marker emission from per-iteration (inside the task fn) to a single BENCHMARK_START/BENCHMARK_END pair bracketing the whole bench run in setupBenchMethods. Each addMarker call is a synchronous FIFO round-trip to the runner, so per-iteration markers scaled with iteration count (millions for fast benches), overwhelmed the runner, and timed out the walltime CI job — while also inflating the measured samples. Emission is gated to walltime mode so the analysis runner sharing setupBenchMethods is unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
5 hours ago
fix(tinybench): emit a single walltime marker pair per task Per-iteration markers made marker volume proportional to the iteration count (millions for fast benches): every addMarker call is a synchronous FIFO round-trip to the runner, which overwhelmed it and timed out the walltime CI job. Buffer round timestamps in JS instead and flush one BENCHMARK_START/BENCHMARK_END pair bracketing the measured rounds after the run. Also exclude warmup from markers (the wrapper previously emitted markers during warmup rounds) and fix the sync path to use warmupSync(): the un-awaited async warmup() never actually ran before runSync(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
6 hours ago
chore: try with intel mac
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
6 hours ago
chore: disable other CI jobs
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
8 hours ago
Latest Branches
CodSpeed Performance Gauge
+3%
feat: add MacOS support
#81
4 hours ago
93cf800
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
CodSpeed Performance Gauge
+8%
Add playwright profiling package
#80
8 days ago
1d2e682
cod-2721-electron-profiling-package-scripts-and-write-docs-about-how
CodSpeed Performance Gauge
-30%
Support macos walltime without profiling in codspeed-node
#79
2 months ago
42a33dd
cod-2459-be-able-to-run-all-integrations-on-macos
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs