Skip to content

feat: basic benchmarking#378

Merged
m4tx merged 7 commits into
masterfrom
basic-benchmarking
Aug 22, 2025
Merged

feat: basic benchmarking#378
m4tx merged 7 commits into
masterfrom
basic-benchmarking

Conversation

@seqre

@seqre seqre commented Jul 10, 2025

Copy link
Copy Markdown
Member

No description provided.

@seqre seqre self-assigned this Jul 10, 2025
@github-actions github-actions Bot added C-lib Crate: cot (main library crate) A-ci Area: CI (Continuous Integration) labels Jul 10, 2025
@seqre seqre changed the title Basic benchmarking feat: basic benchmarking Jul 11, 2025
@seqre seqre force-pushed the basic-benchmarking branch from a890711 to 594c45c Compare July 28, 2025 13:10
@github-actions

github-actions Bot commented Jul 28, 2025

Copy link
Copy Markdown

🐰 Bencher Report

Branchbasic-benchmarking
Testbedgithub-ubuntu-latest

⚠️ WARNING: No Threshold found!

Without a Threshold, no Alerts will ever be generated.

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds flag.

Click to view all benchmark results
BenchmarkLatencymicroseconds (µs)
empty_router/empty_router📈 view plot
⚠️ NO THRESHOLD
5,994.90 µs
json_api/json_api📈 view plot
⚠️ NO THRESHOLD
994.68 µs
nested_routers/nested_routers📈 view plot
⚠️ NO THRESHOLD
931.57 µs
single_root_route/single_root_route📈 view plot
⚠️ NO THRESHOLD
888.36 µs
single_root_route_burst/single_root_route_burst📈 view plot
⚠️ NO THRESHOLD
17,363.00 µs
🐰 View full continuous benchmarking report in Bencher

@seqre seqre force-pushed the basic-benchmarking branch 2 times, most recently from 313fa61 to 840b7c3 Compare July 28, 2025 13:42
@seqre seqre marked this pull request as ready for review July 28, 2025 13:43
@seqre seqre requested a review from m4tx July 28, 2025 14:06

@m4tx m4tx left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work! A few comments from me.

Should we set up some thresholds so that bencher stops complaining about them not being set in the GH comment it creates?

Comment thread cot/Cargo.toml Outdated
Comment thread cot/Cargo.toml Outdated
Comment thread cot/benches/bench_utils.rs Outdated
Comment thread cot/benches/bench_utils.rs Outdated
Comment thread cot/benches/bench_utils.rs Outdated
Comment thread cot/benches/router.rs Outdated
@seqre seqre force-pushed the basic-benchmarking branch from cd39fe1 to b713847 Compare August 4, 2025 15:13
@seqre seqre requested a review from m4tx August 4, 2025 15:13
@codecov

codecov Bot commented Aug 4, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
rust 89.77% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@m4tx m4tx left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per my last review:

Should we set up some thresholds so that bencher stops complaining about them not being set in the GH comment it creates?

Also, can we add some information about how benches work, their configuration, etc. to CONTRIBUTING.md?

Comment thread cot/benches/bench_utils.rs Outdated
Comment thread cot/benches/bench_utils.rs Outdated
@seqre

seqre commented Aug 17, 2025

Copy link
Copy Markdown
Member Author

As per my last review:

Should we set up some thresholds so that bencher stops complaining about them not being set in the GH comment it creates?

They were already added back then here, but until bencher runs at least once on master, it has nothing to compare against, so we won't see changes in the PR message until its merged.

@seqre seqre requested a review from m4tx August 17, 2025 16:39
@m4tx

m4tx commented Aug 22, 2025

Copy link
Copy Markdown
Member

As per my last review:

Should we set up some thresholds so that bencher stops complaining about them not being set in the GH comment it creates?

They were already added back then here, but until bencher runs at least once on master, it has nothing to compare against, so we won't see changes in the PR message until its merged.

Looking good; just please make sure the benchmarks work as intended in the future PRs!

@m4tx m4tx left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good stuff; let's see how it works in practice!

@m4tx m4tx merged commit 433c0a9 into master Aug 22, 2025
38 checks passed
@m4tx m4tx deleted the basic-benchmarking branch August 22, 2025 21:21
@cotbot cotbot Bot mentioned this pull request Aug 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-ci Area: CI (Continuous Integration) C-lib Crate: cot (main library crate)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants