CodSpeedHQ/codspeed-rust - CodSpeed

codspeed-rust

Blog Docs Changelog

Performance History

Latest Results

feat(codspeed): time each benchmark with round markers (#201) The runner times a benchmark when it receives the commands that start and stop it, a while before the benchmark starts and after it ends: tens of microseconds, longer than many benchmarks. Time each benchmark in the process too, right after the start command and right after the benchmarked code returns, outside of the measured section, and send these bounds as round markers before the stop command. They are sent whatever the instrumentation status: instrument hooks drops them outside of the CodSpeed runner and under Valgrind. Only the builds that run each benchmark once, under `cfg(codspeed)`, send them: the native harness also runs in walltime builds, whose rounds are the walltime loop's. Refs COD-3862 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

main

2 hours ago

perf(codspeed): warm the telemetry up before the benchmarks run The first span of the process takes 20 to 30 µs longer than the next ones to go through the subscriber, and the first event about 10 µs longer. The first benchmark emitting them took that time, which delayed its telemetry from the start of its run. `init` now emits a span and an event once the subscriber is installed. They carry a `codspeed_warmup` field, which the processors in front of the exporters drop, and a target the filter always lets through at the `error` level, which keeps the max level `log` takes from the filter. Refs COD-3862 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

cod-3862-featrust-otel-cargo-feature-in-codspeed-divan-compat

1 day ago

perf(codspeed): warm the telemetry up before the benchmarks run The first span of the process takes 20 to 30 µs longer than the next ones to go through the subscriber, and the first event about 10 µs longer. The first benchmark emitting them took that time, which delayed its telemetry from the start of its run. `init` now emits a span and an event once the subscriber is installed. They carry a `codspeed_warmup` field, which the processors in front of the exporters drop, and a target the filter always lets through at the `error` level, which keeps the max level `log` takes from the filter. Refs COD-3862 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

cod-3862-featrust-otel-cargo-feature-in-codspeed-divan-compat

4 days ago

perf(codspeed): warm the telemetry up before the benchmarks run The first span of the process takes 20 to 30 µs longer than the next ones to go through the subscriber, and the first event about 10 µs longer. The first benchmark emitting them took that time, which delayed its telemetry from the start of its run. `init` now emits a span and an event once the subscriber is installed. They carry a `codspeed_warmup` field, which the processors in front of the exporters drop, and a target the filter always lets through at the `error` level, which keeps the max level `log` takes from the filter. Refs COD-3862 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

cod-3862-featrust-otel-cargo-feature-in-codspeed-divan-compat

4 days ago

perf(codspeed): warm the telemetry up before the benchmarks run The first span of the process takes 20 to 30 µs longer than the next ones to go through the subscriber, and the first event about 10 µs longer. The first benchmark emitting them took that time, which delayed its telemetry from the start of its run. `init` now emits a span and an event once the subscriber is installed. They carry a `codspeed_warmup` field, which the processors in front of the exporters drop, and a target the filter always lets through at the `error` level, which keeps the max level `log` takes from the filter. Refs COD-3862 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

cod-3862-featrust-otel-cargo-feature-in-codspeed-divan-compat

4 days ago

perf(codspeed): warm the telemetry up before the benchmarks run The first span of the process takes 20 to 30 µs longer than the next ones to go through the subscriber, and the first event about 10 µs longer. The first benchmark emitting them took that time, which delayed its telemetry from the start of its run. `init` now emits a span and an event once the subscriber is installed. They carry a `codspeed_warmup` field, which the processors in front of the exporters drop, and a target the filter always lets through at the `error` level, which keeps the max level `log` takes from the filter. Refs COD-3862 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

cod-3862-featrust-otel-cargo-feature-in-codspeed-divan-compat

4 days ago

feat(codspeed): time each benchmark with round markers The runner times a benchmark when it receives the commands that start and stop it, a while before the benchmark starts and after it ends: tens of microseconds, longer than many benchmarks. Time each benchmark in the process too, right after the start command and right after the benchmarked code returns, outside of the measured section, and send these bounds as round markers before the stop command. They are sent whatever the instrumentation status: instrument hooks drops them outside of the CodSpeed runner and under Valgrind. Only the builds that run each benchmark once, under `cfg(codspeed)`, send them: the native harness also runs in walltime builds, whose rounds are the walltime loop's. Refs COD-3862 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

feat/time-benchmarks-with-round-markers

4 days ago

feat(codspeed): time each benchmark with round markers The runner times a benchmark when it receives the commands that start and stop it, a while before the benchmark starts and after it ends: tens of microseconds, longer than many benchmarks. Time each benchmark in the process too, right after the start command and right after the benchmarked code returns, outside of the measured section, and send these bounds as round markers before the stop command. They are sent whatever the instrumentation status: instrument hooks drops them outside of the CodSpeed runner and under Valgrind. Only the builds that run each benchmark once, under `cfg(codspeed)`, send them: the native harness also runs in walltime builds, whose rounds are the walltime loop's. Refs COD-3862 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

feat/time-benchmarks-with-round-markers

5 days ago

Latest Branches

-4%

feat: export the telemetry of divan benchmarks over OTLP#197

5 days ago

1e3f5f8

cod-3862-featrust-otel-cargo-feature-in-codspeed-divan-compat

-5%

feat(codspeed): time each benchmark with round markers#201

5 days ago

5b54240

feat/time-benchmarks-with-round-markers

+4%

feat(codspeed): declare a Symposium plugin#200

6 days ago

28908bc

cod-3968-ship-codspeed-skills-and-mcp-to-symposium-cargo-agents-users

© 2026 CodSpeed Technology

Home Terms Privacy Docs