Token-cost benchmarking for `img2threejs` model generation pipeline.
Raw Developer Origin & Technical Request
GitHub Issue
Jul 17, 2026
## Motivation
The numbers in `docs/TOKEN_COST.md` are honest **engineering estimates**, not a measurement. Replacing them with a reproducible benchmark makes the token-efficiency claim credible and lets us track regressions.
## Scope
- A harness that runs N full reconstructions (fixed reference set) and records **real model-token spend** per stage (assessment, spec, codegen, each render-review cycle).
- Emit a table + per-stage breakdown, and a delta vs. the previous run.
- Keep it deterministic where possible so results are comparable across runs.
## Pointers
- `docs/TOKEN_COST.md` (the estimate tables to replace)
- `ROADMAP.md` (v1.5 — "measured token-cost benchmark replacing the current estimates")
## Acceptance criteria
- `scripts/benchmark_token_cost.py` (pure-stdlib, matching the repo's zero-dep tooling) produces a measured cost table.
- `docs/TOKEN_COST.md` gains a "Measured" section alongside the estimates.
**Difficulty:** medium · **Labels:** good first issue for someone who wants to learn the pipeline end to end.
Developer Debate & Comments
No active discussions extracted for this entry yet.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from hoainho/img2threejs.
Frequently Asked Questions
Market intelligence mapped to Token-cost benchmarking for `img2threejs` model generation pipeline..
What problem does Token-cost benchmarking for `img2threejs` model generation pipeline. solve?
What architecture is tied to Token-cost benchmarking for `img2threejs` model generation pipeline.?
Engagement Signals
Cross-Market Term Frequency
Counts stored text matches for foundational terms like spec and deterministic in analysed public discussions. These counts do not measure adoption.
Stored text matches, not adoption or market-share measurements.
- spec: 106 records
- deterministic: 30 records
- codegen: 5 records
- assessment: 4 records
- token-cost benchmark: 1 records
- engineering estimates: 1 records
- reproducible benchmark: 1 records
- model-token spend: 1 records
- render-review cycle: 1 records
- per-stage breakdown: 1 records
- delta vs. previous run: 1 records
- pure-stdlib: 1 records
- zero-dep tooling: 1 records
SaaS Metrics