Closed
Bug 1216406
Opened 9 years ago
Closed 8 years ago
Investigate gecko performance regression between 2.2 and 2.5
Categories
(Firefox OS Graveyard :: Performance, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bobby.chien+bugzilla, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: perf, regression, Whiteboard: [Profile-wanted])
Investigate potential Gecko regression issue per bug 1210440, comment 13.
Comment 1•9 years ago
|
||
Bobby, Ting mentioned in another bug that time is spent on parsing JS. Can we get all the gecko/JS parsing issues identified from previous profiling efforts into separate bugs and have gecko engineers investigate and fix please. Thanks Hema
blocking-b2g: --- → 2.5+
Flags: needinfo?(bchien)
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Hema Koka [:hema] from comment #1) > Bobby, > > Ting mentioned in another bug that time is spent on parsing JS. Can we get > all the gecko/JS parsing issues identified from previous profiling efforts > into separate bugs and have gecko engineers investigate and fix please. > > Thanks > Hema No, Ting mentioned about too many JS files need to be parsed, so loading takes too long. Not about JS parsing speed is slow. As current study, we found most apps already use lazy loading technique. So suppose it's not major issue in gaia app. I also didn't see big regression in JS engine in gecko. So I assume JS relative issue is not major issue for this investigation. I will work with Ting to dig more in this bug. Thanks.
Flags: needinfo?(bchien)
Updated•9 years ago
|
Blocks: TV_Gecko_P2
Comment 3•9 years ago
|
||
Please look at bug 1162535 for memory usage regression as well.
Reporter | ||
Comment 4•9 years ago
|
||
[Tracking Requested - why for this release]: Need more time to investigate regression. Plan in next version.
Updated•9 years ago
|
No longer blocks: TV_Gecko_P2
Reporter | ||
Updated•8 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•