Measure NFR-1 against hono - #37
Conversation
Three of the four targets pass with 20-50x of headroom: 358 files cloned, parsed, resolved and written in 3.9s against a 90s budget; functions-for-file p95 3.1ms against 150ms; a 5-hop traversal 4.4ms p95, 9.1ms worst case, against 500ms. The fourth could not be tested at its stated scale. Opening and expanding every function in hono's largest file produces 210 nodes, and nothing on this repository approaches the 2,000-node ceiling. What was measured at 210 nodes is recorded rather than extrapolated. Two traps found by running it, both recorded so the next person does not lose an hour to them. The parser's summary counts call sites and the database stores deduplicated edges, so 37,116 against 5,292 is not a discrepancy. And the API rate-limits at 100 requests a minute, which the first latency run silently measured instead of the API -- 429s are fast. That second one is R40: it also means a restored canvas with many open branches can spend the budget on one load.
|
Warning Review limit reachedNext included review available in 33 minutes. View limit detailsLimit details: You’ve used the included review currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (4)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/settings/billing. Comment |
1 participant
No description provided.