use codspeed to keep track of performances

[sylvestre]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.31%. Comparing base (9c5479e) to head (dd23220).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #212   +/-   ##
=======================================
  Coverage   82.31%   82.31%           
=======================================
  Files          13       13           
  Lines        5371     5371           
  Branches      293      293           
=======================================
  Hits         4421     4421           
  Misses        948      948           
  Partials        2        2           

Flag	Coverage Δ
macos_latest	82.75% <ø> (ø)
ubuntu_latest	82.86% <ø> (ø)
windows_latest	0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[codspeed-hq]

CodSpeed Performance Report

Congrats! CodSpeed is installed 🎉

🆕 11 new benchmarks were detected.

You will start to see performance impacts in the reports once the benchmarks are run from your default branch.

Detected benchmarks

• access_log_no_op: 746.4 ms
• access_log_all_del: 542.1 ms
• access_log_no_del: 501 ms
• remove_cr: 273.4 ms
• access_log_subst: 1.2 s
• access_log_append: 635.3 ms
• access_log_no_subst: 494.9 ms
• genome_subst: 211.4 ms
• access_log_translit: 784.3 ms
• no_op_short: 961.2 ms
• number_fix: 507.7 ms

[cakebaker]

Looks good to me.

In sed_bench.rs there is probably some potential for performance improvements. For example, using with_capacity instead of new.