>From what I understand, launch times and memory usage are both underground
>large regressions right now from the preallocated process bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1151672
Also, Raptor tracks memory usage for applications as part of the cold launch
test, and is run with incoming Gaia commits:
http://raptor-ui.divshot.io/#/dashboard/script/memory.js?device=flame-kk&branch=master&memory=319&suite=coldlaunch
Thanks,
Eli Perelman
On Thu, May 7, 2015 at 8:32 AM, Nicolas B. Pierron
<[email protected]> wrote:
> On 05/07/2015 02:59 PM, Gabriele Svelto wrote:
>>> On 03/25/2015 5:49 PM, Kyle Huey wrote:
>>>
>>> Previous experience suggests that if we relax the limits at all it's going
>>> to be quite difficult to claw that back.
>>>
>>> Somebody should take some memory reports from 2.2 and trunk and diff them,
>>> so we can start looking at where the fat is.
>>
>> After much procrastinating I finally managed to carve some time to do a
>> diff between v2.1, v2.2 and master and frankly the results are
>> worrisome. I've made a clean install of the three engineering builds and
>> opened some applications with empty workloads (dialer, sms, gallery,
>> music, clock and settings) and gathered memory reports after having
>> minimized all of them. Here's the bird's eye view of the three branches
>> by USS:
> Is there anybody looking into adding this procedure (or similar) as
> performance tests which are reported daily? In order to know when this
> issue is fixed, and to watch for regressions later.
> --
> Nicolas B. Pierron
> _______________________________________________
> dev-b2g mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
