Chat rendering performance
Open
Nobody has claimed this yet.
feature: frontend 🖌️
Needs triage
performance 🚀
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Steps to reproduce
- Try to re-render a chat
- See performance report
- Recalculate style triggers Forced reflow, which delays re-rendering of new frame
Recalculate style->NcActions->useElementBounding
- Check upstream, if possible to avoid
- temporary - comment out TopBarMenu component
Recalculate style->MessagesList->checkChatNotScrollable
- Check, if could be delayed / moved to nextTick
- temporary - comment out method
Recalculate style->Mention->mounted
- Check, if CSS transform is good enough to adjust height
- Check upstream, if
inline-sizeprop can be implememented - temporary - set to fixed value
With temporary solutions task takes ~630ms
Without temporary solutions - ~660ms
Not a big win, but feels like we can benefit from avoiding sync recalculate
Contributor guide
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 performance report and inspect the three listed paths: NcActions/useElementBounding, MessagesList/checkChatNotScrollable, and Mention/mounted. Check the relevant upstream behavior and whether the suggested delayed or fixed-value alternatives are viable. Done means reducing synchronous style recalculation during chat re-rendering and comparing the result with the reported ~630–660ms timings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100