914875 - [e.me][meta] v1.3 homescreen performance

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Everything.me, defect, P1)

Description

[Ran Ben Aharon [:ranbena] EverythingMe]

After clicking a collection, homescreen panning deteriorates.

Comment 1

[Ran Ben Aharon [:ranbena] EverythingMe]

PR branch
https://github.com/EverythingMe/gaia/tree/914875-homescreen-perf

Comment 2

[Amir Nissim (:amirn)]

CP to stg-pr branch
https://github.com/EverythingMe/gaia/commit/08f571a208d6ec6b6939d69f606d46fd20b6cd3b

Comment 3

[Mike Lee [:mlee]]

What's the work needed here?

Comment 4

[Ran Ben Aharon [:ranbena] EverythingMe]

Hey Mike, all the related tickets for this bug have already been in implemented. All have been landed as well (apart for 919555).
The target was reducing memory footprint, restoring panning fps and making sure app load times weren't affected.

Comment 5

[Mike Lee [:mlee]]

Thanks Ran. Marking this as a meta bug.

Comment 6

[Jason Smith [:jsmith]]

(In reply to Mike Lee [:mlee] from comment #5)
> Thanks Ran. Marking this as a meta bug.

Meta bugs are fine to use, but they don't block the release, as they aren't actionable in itself. This needs to be removed from the blocking list.

Comment 7

[Ran Ben Aharon [:ranbena] EverythingMe]

So if I understand correctly, I should remove the block from this bug and add it to all the dependent ones?

Comment 8

[Jason Smith [:jsmith]]

(In reply to Ran Ben Aharon (Everything.me) from comment #7)
> So if I understand correctly, I should remove the block from this bug and
> add it to all the dependent ones?

Yeah. The dependencies should be nominated that are perf-related blockers. The meta bug doesn't need to block.

Comment 9

[Jason Smith [:jsmith]]

Clearing nom - we're no longer taking e.me 1.2 feature changes to 1.2.