If you would like to use Raptor to start performance testing your apps to
get these numbers down, it's all documented on MDN [1]. These numbers were
captured on a Flame-KK with 319MB of memory with the light reference
workload, which is the baseline device for v2.2 -> v2.5. Raptor does
require Node v0.12 [2], so if you find you need to switch between Node 0.10
and 0.12 for Gaia, I recommend something like "n" [3] to easily switch
between.

[1] https://developer.mozilla.org/en-US/Firefox_OS/Automated_testing/Raptor
[2]
https://developer.mozilla.org/en-US/Firefox_OS/Automated_testing/Raptor#Prerequisites
[3] https://www.npmjs.com/package/n

Thanks,

Eli


On Fri, Oct 2, 2015 at 10:54 AM, Gareth Aye <[email protected]> wrote:

> muy cache!
>
> On Fri, Oct 2, 2015 at 11:37 AM, Wilson Page <[email protected]> wrote:
>
>> Wow! Can email share what changes they made to get such a big improvement?
>>
>> *W I L S O N  P A G E*
>>
>> Front-end Developer
>> Firefox OS (Gaia)
>> London Office
>>
>> Twitter: @wilsonpage
>> IRC: wilsonpage
>>
>> On Fri, Oct 2, 2015 at 3:51 PM, Eli Perelman <[email protected]>
>> wrote:
>>
>>> Hello fxos,
>>>
>>> With deadlines for v2.5 approaching, I thought I would take a couple
>>> minutes and summarize the current state of performance for Gaia. At the
>>> outset of v2.5 we captured metrics of v2.2 and have used that as the
>>> baseline to determine whether applications have regressed their performance
>>> since. Any applications whose performance has significantly regressed since
>>> v2.2 will need approval to not block as major increases will block v2.5.
>>>
>>> Enough of the chatter, here's the data:
>>>
>>> Calendar v2.2 cold launch: 1454ms
>>> Calendar current cold launch: 1638ms (~180ms regression)
>>> Calendar v2.2 USS: 14.01MB
>>> Calendar current USS: 13.99MB (good)
>>>
>>> Camera v2.2 cold launch: 1492ms
>>> Camera current cold launch: 2090ms (~600ms regression)
>>> Camera v2.2 USS: 13.83MB
>>> Camera current USS: 16.05MB (~2.2MB regression)
>>>
>>> Clock v2.2 cold launch: 1232ms
>>> Clock current cold launch: 1260ms (acceptable)
>>> Clock v2.2 USS: 13.98MB
>>> Clock current USS: 14.95MB (~1MB regression)
>>>
>>> Contacts v2.2 cold launch: 773ms
>>> Contacts current cold launch: 1246ms (~475ms regression)
>>> Contacts v2.2 USS: 18.26MB
>>> Contacts current USS: 20.04MB (~1.75MB regression)
>>>
>>> Dialer v2.2 cold launch: 851ms
>>> Dialer current cold launch: 944ms (~90ms regression, still under 1000ms)
>>> Dialer v2.2 USS: 17.48MB
>>> Dialer current USS: 13.04MB (good!)
>>>
>>> Email v2.2 cold launch: 2129ms
>>> Email current cold launch: 606ms (good!)
>>> Email v2.2 USS: 16.17MB
>>> Email current USS: 15.78MB (good)
>>>
>>> FM v2.2 cold launch: 604ms
>>> FM current cold launch: 783ms (~175ms regression)
>>> FM v2.2 USS: 10.37MB
>>> FM current USS: 10.51MB (acceptable)
>>>
>>> Gallery v2.2 cold launch: 1113ms
>>> Gallery current cold launch: 1207ms (~90ms regression)
>>> Gallery v2.2 USS: 17.71MB
>>> Gallery current USS: 18.98MB (~1.25MB regression)
>>>
>>> Music v2.2 cold launch: 1066ms
>>> Music current cold launch: 1717ms (~650ms regression)
>>> Music v2.2 USS: 13.37MB
>>> Music current USS: 29.49MB (~16.12MB regression)
>>>
>>> SMS v2.2 cold launch: 1340ms
>>> SMS current cold launch: 1630ms (~290ms regression)
>>> SMS v2.2 USS: 12.86MB
>>> SMS current USS: 19.94MB (~7MB regression)
>>>
>>> Settings v2.2 cold launch: 2474ms
>>> Settings current cold launch: 2950ms (~475ms regression)
>>> Settings v2.2 USS: 17.18MB
>>> Settings current USS: 17.54MB (acceptable)
>>>
>>> Video v2.2 cold launch: 1115ms
>>> Video current cold launch: 1309ms (~190ms regression)
>>> Video v2.2 USS: 12.13MB
>>> Video current USS: 13MB (acceptable)
>>>
>>> TLDR; there seem to be quite a few serious regressions across many
>>> applications, in both cold launch time and USS memory usage. As a
>>> comparison, the Test Startup Limit app when first captured started off in
>>> the 880ms range, spent a good chunk of June and July around 620ms and is
>>> now around 850ms.
>>>
>>> If anyone has any questions about the data or needs additional
>>> information, please let me know.
>>>
>>> Also, kudos to the Email team for the massive improvement in both launch
>>> time and memory.
>>>
>>> Thanks,
>>>
>>> Eli Perelman
>>>
>>> _______________________________________________
>>> dev-fxos mailing list
>>> [email protected]
>>> https://lists.mozilla.org/listinfo/dev-fxos
>>>
>>>
>>
>> _______________________________________________
>> dev-fxos mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-fxos
>>
>>
>
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to