1216406 - Investigate gecko performance regression between 2.2 and 2.5

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Performance, defect, P2)

Description

[Bobby Chien]

Investigate potential Gecko regression issue per bug 1210440, comment 13.

Comment 1

[Hema Koka [:hema]]

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

Comment 2

[Bobby Chien]

(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.

Comment 3

[Julien Wajsberg [:julienw]]

Please look at bug 1162535 for memory usage regression as well.

Comment 4

[Bobby Chien]

[Tracking Requested - why for this release]: 
Need more time to investigate regression. Plan in next version.