emberjs / emberjs/ember-inspector
Proposal: Enhanced Render Performance Dashboard for Ember Inspector
- Dominant language
- JavaScript
- Stars
- 969
- Forks
- 292
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Yes. The current Render Performance panel in Ember Inspector shows a raw list of component render timings. While useful, it requires developers to manually scan through long tables to identify bottlenecks. In larger apps, this process becomes time-consuming and error-prone, making it more difficult to act quickly on performance data.
**Describe the solution you'd like**
I’d like to enhance this panel into an Enhanced Render Performance Dashboard with:
- A Summary View that highlights the “Top N slowest components,” shows average render vs. re-render times, and tracks re-render frequency.
- A future timeline/profiler view (similar to React DevTools Profiler) to visualise when renders happen and correlate them with user interactions.
** Describe alternatives you've considered **
- Relying on external profiling tools (e.g., browser Performance tab), but these lack Ember-specific insights.
- Manually filtering and analysing the existing raw render timings list, but this doesn’t scale well for larger applications.
** Additional context **
This feature would:
- Help developers identify bottlenecks at a glance.
- Provide actionable insights beyond raw data.
- Improve overall productivity and developer experience with Ember Inspector.
If maintainers agree, I’d be happy to take ownership of this issue and start with the MVP (Summary View first), then iterate with community feedback.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the current Render Performance panel and reviewing how its raw component render timings are collected and displayed. The proposed MVP is a Summary View showing the top N slowest components, average render and re-render times, and re-render frequency; the issue names no files or tests, so acceptance details need to be established first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100