Skip to content

docs: update incremental benchmarks (3.0.1)#323

Merged
carlos-alm merged 1 commit intomainfrom
benchmark/incremental-v3.0.1-20260304-050123
Mar 4, 2026
Merged

docs: update incremental benchmarks (3.0.1)#323
carlos-alm merged 1 commit intomainfrom
benchmark/incremental-v3.0.1-20260304-050123

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 4, 2026

Automated incremental benchmark update for 3.0.1 from workflow run #190.

@greptile-apps
Copy link

greptile-apps bot commented Mar 4, 2026

Greptile Summary

Automated benchmark update for v3.0.1 reflecting expected performance impact from enabling CFG and dataflow analysis by default.

  • Native full build increased from 721ms to 2.3s (+223%) and 1-file rebuild from 325ms to 928ms (+186%)
  • These regressions are expected per the 3.0.1 CHANGELOG, which documents that --cfg and --dataflow are now enabled by default on builds (PR feat: enable --cfg and --dataflow by default on builds #312)
  • All benchmark data is correctly formatted with accurate percentage calculations
  • JSON data matches the displayed tables

Confidence Score: 5/5

  • This PR is safe to merge with no risk
  • Automated documentation update with accurate benchmark data that correctly reflects expected performance characteristics of v3.0.1
  • No files require special attention

Important Files Changed

Filename Overview
generated/benchmarks/INCREMENTAL-BENCHMARKS.md Added v3.0.1 benchmark data showing expected performance impact from enabling --cfg and --dataflow by default

Last reviewed commit: 6efce30

@carlos-alm carlos-alm merged commit 358659a into main Mar 4, 2026
@carlos-alm carlos-alm deleted the benchmark/incremental-v3.0.1-20260304-050123 branch March 4, 2026 05:03
@github-actions github-actions bot locked and limited conversation to collaborators Mar 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant