Closed
Bug 993318
Opened 11 years ago
Closed 11 years ago
[Settings] build script improvement for load time
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
1.4 S6 (25apr)
People
(Reporter: gasolin, Assigned: gasolin)
References
Details
Attachments
(1 file)
We'd improve settings load time via
* use better r.js config to minimize production source
And it might worth to remove the data-skip-optimize hack in index.html by create new startup.js (as camera does).
Assignee | ||
Comment 1•11 years ago
|
||
And please append b2gperf load time result in real device with `GAIA_OPTIMIZE=1 make production` build.
Updated•11 years ago
|
Target Milestone: --- → 1.4 S6 (25apr)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gasolin
Assignee | ||
Comment 2•11 years ago
|
||
refer from email app,
performance test 1684 -> 1648
only do the uglify while production
Attachment #8404607 -
Flags: review?(arthur.chen)
Comment 3•11 years ago
|
||
Comment on attachment 8404607 [details] [review]
pull request redirect to github
Thanks for the patch.
I think we should turn off beautify and turn on compress and mangle. That's what webapp-optimize.js does for production builds.
Attachment #8404607 -
Flags: review?(arthur.chen)
Assignee | ||
Comment 4•11 years ago
|
||
Comment on attachment 8404607 [details] [review]
pull request redirect to github
- use startup.js to load main.js,
- do mangling and compress.
- update to alameda from 0.0.9 to 0.2
got load time 1742 -> 1613
Attachment #8404607 -
Flags: review?(arthur.chen)
Comment 5•11 years ago
|
||
Comment on attachment 8404607 [details] [review]
pull request redirect to github
r=me, thank you for the patch!
Attachment #8404607 -
Flags: review?(arthur.chen) → review+
Assignee | ||
Comment 6•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 7•11 years ago
|
||
This change breaks make test-perf.
Filed bug 1011168
Comment 8•11 years ago
|
||
I'll be honest I don't know how it cause breakage. But I do have a fix.
You need to log in
before you can comment on or make changes to this bug.
Description
•