Skip to content

docs: update build performance benchmarks (v2.4.0)#148

Closed
github-actions[bot] wants to merge 1 commit intomainfrom
benchmark/build-v2.4.0-20260227-041058
Closed

docs: update build performance benchmarks (v2.4.0)#148
github-actions[bot] wants to merge 1 commit intomainfrom
benchmark/build-v2.4.0-20260227-041058

Conversation

@github-actions
Copy link
Contributor

Automated build benchmark update for v2.4.0 from workflow run #74.

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 27, 2026

Greptile Summary

Automated benchmark update for v2.4.0 that documents current build and query performance on the project's own codebase.

  • Updated performance metrics in both README.md and generated/BUILD-BENCHMARKS.md
  • Benchmarks reveal significant performance regression: native build speed degraded from 2.1 ms/file to 6.7 ms/file (253% increase), likely due to new complexity analysis features in feat: multi-language complexity analysis #147
  • File count increased from 109 to 122 files (+13 files)
  • Found data inconsistencies: raw totals show unified query times (3ms for both engines) but version table and JSON correctly differentiate between native (2.5ms) and WASM (3.4ms)

Confidence Score: 4/5

  • Safe to merge after fixing query time inconsistencies
  • Documentation-only PR from automated workflow with no code changes. Minor data inconsistencies in query time reporting should be fixed, but don't affect functionality. The performance regression revealed by these benchmarks was introduced in previous PRs, not this one.
  • Fix the query time values in generated/BUILD-BENCHMARKS.md raw totals sections to match the version table and JSON data

Important Files Changed

Filename Overview
README.md Updated performance table with v2.4.0 benchmarks showing increased build times and new query metrics
generated/BUILD-BENCHMARKS.md Comprehensive benchmark report updated with v2.4.0 data; contains minor inconsistencies in query time reporting

Last reviewed commit: e6246f4

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

2 files reviewed, 2 comments

Edit Code Review Agent Settings | Greptile

Comment on lines +23 to +28
| Build time | 813ms |
| Query time | 3ms |
| Nodes | 769 |
| Edges | 1,326 |
| DB size | 656 KB |
| Files | 122 |
Copy link
Contributor

Choose a reason for hiding this comment

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

Raw totals show both engines with 3ms query time, but the version table (line 8-9) and JSON data show native: 2.5ms and wasm: 3.4ms. These values should match.

Suggested change
| Build time | 813ms |
| Query time | 3ms |
| Nodes | 769 |
| Edges | 1,326 |
| DB size | 656 KB |
| Files | 122 |
| Build time | 813ms |
| Query time | 2.5ms |
| Nodes | 769 |
| Edges | 1,326 |
| DB size | 656 KB |
| Files | 122 |

Comment on lines +34 to +39
| Build time | 1.2s |
| Query time | 3ms |
| Nodes | 769 |
| Edges | 1,326 |
| DB size | 656 KB |
| Files | 122 |
Copy link
Contributor

Choose a reason for hiding this comment

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

WASM query time should be 3.4ms to match the version table (line 9) and JSON data, not 3ms.

Suggested change
| Build time | 1.2s |
| Query time | 3ms |
| Nodes | 769 |
| Edges | 1,326 |
| DB size | 656 KB |
| Files | 122 |
| Build time | 1.2s |
| Query time | 3.4ms |
| Nodes | 769 |
| Edges | 1,326 |
| DB size | 656 KB |
| Files | 122 |

@carlos-alm carlos-alm closed this Feb 27, 2026
@carlos-alm carlos-alm deleted the benchmark/build-v2.4.0-20260227-041058 branch February 27, 2026 05:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant