Skip to content

Add iPhone XS to our device lab #34590

Closed
Closed

Description

@liyuqian

To monitor our performance on newer iPhones.

We'll later use this to test our metal performances too.

Activity

  1. added
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    c: performanceRelates to speed or footprint issues (see "perf:" labels)
    on Jun 17, 2019
  2. liyuqian commented on Jul 3, 2019

    @liyuqian
    ContributorAuthor

    This would also help #31086

  3. liyuqian commented on Jul 3, 2019

    @liyuqian
    ContributorAuthor

    We've setup mac8 with iPhone X (currently in my desk instead of in the lab). I'll close the issue once we've done some successful performance benchmarks through #35556

  4. self-assigned this
    on Jul 3, 2019
  5. MisterJimson commented on Jul 4, 2019

    @MisterJimson

    FYI I believe it's the XS, not the X, that has the higher sampling rate that causes performance issues. Just want to make sure you are setting up the correct device.

  6. changed the title [-]Add iPhone X to our device lab[/-] [+]Add iPhone XS to our device lab[/+] on Jul 6, 2019
  7. liyuqian commented on Jul 6, 2019

    @liyuqian
    ContributorAuthor

    Luckily, we did buy the iPhone XS as Apple is no longer selling iPhone X on its website :) Edit the title of this issue to reflect that.

  8. liyuqian commented on Jul 31, 2019

    @liyuqian
    ContributorAuthor

    Almost done. I only need to move the Mac Mini and iPhone XS from my desk to the actual lab.

  9. added this to the August 2019 milestone on Aug 7, 2019
  10. liyuqian commented on Aug 8, 2019

    @liyuqian
    ContributorAuthor

    Our lab is currently running out of space. So the device will remain on my desk for a while. The test will keep running.

  11. modified the milestones: August 2019, on Sep 3, 2019
  12. modified the milestones: , December 2019 on Sep 4, 2019
  13. liyuqian commented on Sep 25, 2019

    @liyuqian
    ContributorAuthor

    Moved to the new device lab desk. Closing.

  14. github-actions commented on Aug 27, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  15. locked as resolved and limited conversation to collaborators on Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

c: contributor-productivityTeam-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions