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: nobody → dave.hunt
Status: NEW → ASSIGNED
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.
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)
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.
Priority: -- → P1
Whiteboard: [c=automation p= s= u=]
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
Created attachment 8466175 [details] [diff] [review] Add 319MB and 512MB configurations for Flame. v1.0 This has been running reasonably well.
Attachment #8466175 - Flags: review?(wlachance)
Attachment #8466175 - Flags: review?(wlachance) → review+
Summary: Add a 319MB configuration for the Flame → Add 319MB and 512MB configurations for Flame
You need to log in before you can comment on or make changes to this bug.