Closed
Bug 915088
Opened 12 years ago
Closed 12 years ago
[1.2] SMS App launch time has regressed (compared to [1.1]
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Tracking
(blocking-b2g:koi+)
People
(Reporter: mvikram, Assigned: julienw)
References
Details
(Keywords: perf, regression, Whiteboard: [c=progress p= s= u=1.2] )
Attachments
(1 file)
|
1.78 MB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36
Steps to reproduce:
Launch the SMS App (QRD 7x27 device). Measurements are made using a high speed camera measuring the time from when the touch event was recognized to fist app paint.
Actual results:
Measured time on (1.2) is:
2415 ms
Measured time on (1.1):
1644 ms
| Reporter | ||
Updated•12 years ago
|
| Assignee | ||
Comment 1•12 years ago
|
||
How many threads and SMS do you have in your measurements ?
On Keon this takes 600ms.
Updated•12 years ago
|
blocking-b2g: --- → koi+
| Reporter | ||
Comment 2•12 years ago
|
||
Will it help to attach the SMS DB with the test data?
Updated•12 years ago
|
Keywords: perf,
regression
| Assignee | ||
Comment 3•12 years ago
|
||
Yes please, it will help a lot working on the same data set :)
Flags: needinfo?(mvikram)
| Reporter | ||
Comment 5•12 years ago
|
||
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → felash
Updated•12 years ago
|
Whiteboard: [c=progress p= s= u=1.2]
Comment 6•12 years ago
|
||
Per Sandip in bug 914910: First time launch latency goal for SMS app is 1200ms.
Blocks: 915068
Comment 8•12 years ago
|
||
Julien - this is a CS blocker brought up by QC, are you getting any progress in investigating the regression and/or driving down the launch latency in v1.2 with a forward fix?
Flags: needinfo?(felash)
| Assignee | ||
Comment 9•12 years ago
|
||
I've not investigated much yet, and at least not with the provided attachment yet.
Something planned for this week.
Flags: needinfo?(felash)
Comment 10•12 years ago
|
||
What do I do exactly with that .zip. If I adb push its content to replace /data/local on my device, I don't even get b2g to restart.
I get the following error messages in logcat
E/GeckoConsole( 866): [JavaScript Error: "DOMApplicationRegistry: Could not parse JSON: /data/local/webapps/webapps.json [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.create]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/FileUtils.jsm :: FileUtils_getDir :: line 70" data: no]
E/GeckoConsole( 866): undefined" {file: "resource://gre/modules/Webapps.jsm" line: 863}]
E/GeckoConsole( 866): [JavaScript Error: "[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.create]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/FileUtils.jsm :: FileUtils_getDir :: line 70" data: no]" {file: "resource://gre/modules/FileUtils.jsm" line: 70}]
| Reporter | ||
Comment 11•12 years ago
|
||
These are the steps I followed:
1) Download and extract attached zip file
2) run |adb root|
3) run |adb remount|
4) run |adb push local /data/local|
Also, you can try rebooting the phone.
It works for me.
| Assignee | ||
Comment 12•12 years ago
|
||
I only pushed the sms databases.
Could not get a working 1.2 buri yet.
Updated•12 years ago
|
Target Milestone: --- → 1.2 QE1(Oct11)
| Assignee | ||
Comment 13•12 years ago
|
||
So, I get around 650ms on 1.1 for the first paint, plus around 500ms for showing the first message.
Aaaaaaaand. the same for 1.2.
Both on Buri.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•