A1. Measure Custom View Scene patch throughput
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 66
Description
Does updateCustomView sustain a token-rate text stream, or does it rate-limit? The whole streaming display design assumes it does. Measure patch latency and maximum sustained patch rate; establish the coalescing interval the reducer must impose.
Blocks: #spec-projection-frame-fits realization.
Section A — Hardware verification (needs a Rokid device). Registered from ISSUES.md.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the updateCustomView entry point and the hardware-verification notes in ISSUES.md; run measurements on a Rokid device. Record patch latency and maximum sustained patch rate, then establish the coalescing interval needed by the reducer. Done means the findings resolve the #spec-projection-frame-fits realization blocker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100