Closed
Bug 1133864
Opened 10 years ago
Closed 8 years ago
identify Ember workloads for perf needs
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1352486
Tracking | Status | |
---|---|---|
platform-rel | --- | + |
People
(Reporter: dherman, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [platform-rel-Frameworks][platform-rel-EmberJS])
I'm told there could be significant optimization opportunities identified by the Ember performance suite:
https://github.com/eviltrout/ember-performance
This was mentioned in bug 1097376 and perhaps this bug is a dupe of that. But it would be great to discuss with leaders of both the Discourse web app (which is mentioned on that bug) and the Ember core team to find out what areas they still see big issues.
I'm reaching out to them and inviting them to talk with jandem on #jsapi.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(jdemooij)
Comment 1•9 years ago
|
||
Clearing needinfo. It's on my list (and so are other web frameworks) but the needinfos are distracting.
Flags: needinfo?(jdemooij)
Keywords: perf
Updated•8 years ago
|
platform-rel: --- → ?
Whiteboard: [platform-rel-Frameworks][platform-rel-EmberJS]
Updated•8 years ago
|
platform-rel: ? → +
Updated•8 years ago
|
Blocks: QF-Websites
Updated•8 years ago
|
Comment 2•8 years ago
|
||
Bug 1352486 is actually a dupe of this, but the other bug has better information now.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•