Closed
Bug 1041984
Opened 10 years ago
Closed 10 years ago
Add 319MB and 512MB configurations for Flame
Categories
(Testing Graveyard :: Eideticker, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wlach, Assigned: davehunt)
References
Details
(Keywords: perf, Whiteboard: [c=automation p= s= u=])
Attachments
(1 file)
55.64 KB,
patch
|
wlach
:
review+
|
Details | Diff | Splinter Review |
We should add an eideticker job which uses a 273MB configuration for the Flame, as we're keenly interested in startup performance on this platform.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → dave.hunt
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•10 years ago
|
||
I've added a new build step for setting the memory allocation, and a new DEVICE_MEMORY environment variable. I've also modified DEVICE_ID and DEVICE_NAME to contain the memory assigned. The existing jobs have been renamed and configured for 512MB, and I've created new jobs for 273MB. Going to leave these running for a while, and if everything seems okay I'll push a patch to the eideticker-ci repository.
Flags: needinfo?(dave.hunt)
Assignee | ||
Comment 2•10 years ago
|
||
It appears that the 273MB configuration is hitting issues when restarting B2G after populating contacts. We've also seen that the 273MB configuration is causing less stable builds when running b2gperf and make test-perf. I've heard that we might be considering switching to a 319MB configuration, is this right?
Flags: needinfo?(dave.hunt) → needinfo?(mlee)
Comment 3•10 years ago
|
||
Yes. QA is moving forward with testing and reporting on 319MB configurations. Let's be consistent and do the same so we can compare their findings with Eideticker's.
Assignee | ||
Comment 4•10 years ago
|
||
Okay, I've reconfigured the additional jobs to now set 319MB. This means Eideticker now tests on 319MB and 512MB configurations. Once we have some good results I'll submit a patch to the eideticker-ci repository.
Summary: Add a 273MB configuration for the Flame → Add a 319MB configuration for the Flame
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(dave.hunt)
Assignee | ||
Comment 5•10 years ago
|
||
This has been running reasonably well.
Attachment #8466175 -
Flags: review?(wlachance)
Flags: needinfo?(dave.hunt)
Reporter | ||
Updated•10 years ago
|
Attachment #8466175 -
Flags: review?(wlachance) → review+
Assignee | ||
Updated•10 years ago
|
Summary: Add a 319MB configuration for the Flame → Add 319MB and 512MB configurations for Flame
Comment hidden (obsolete) |
Assignee | ||
Comment 7•10 years ago
|
||
Landed in: https://github.com/mozilla/eideticker-ci/commit/0e4b1dc36ee9a28668337bf042ce246fe94f5101
Updated•7 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•