Skip to content

Track CPU/GPU/Energy usage in our performance benchmarks #33899

Closed
Closed
Track CPU/GPU/Energy usage in our performance benchmarks#33899
Labels
P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)customer: crowdAffects or could affect many people, though not necessarily a specific customer.engineflutter/engine related. See also e: labels.perf: energyPerformance issues related to energy use (power, watts)
Milestone
January Beta Release (1.26)

Description

@liyuqian
liyuqian
opened on Jun 5, 2019

Let's add CPU/GPU/Energy use percentage to all our Flutter driver performance tests. It will be a great addition to our current frame-build/rasterize-time metrics.

We've seen many developers tracking it, filing issues on it, and writing articles about it. It will help us address issues like power usage, performance cost not covered by frame build/rasterize phases, etc.

Activity

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

  3. dnfield commented on Jul 31, 2019

    @dnfield
    dnfield
    on Jul 31, 2019
    Contributor

    We're doing this now in the Android firebase test. We just don't have it reporting anywhere nice yet.

  4. Hixie
    added
    customer: amplify
    severe: customer critical
    on Aug 6, 2019
  5. liyuqian
    added this to the December 2019 milestone on Aug 7, 2019
  6. liyuqian
    changed the title [-]Track CPU/GPU usage in our performance benchmarks[/-] [+]Track CPU/GPU/Energy usage in our performance benchmarks[/+] on Aug 20, 2019

  7. Hixie commented on Aug 28, 2019

    @Hixie
    Hixie
    on Aug 28, 2019
    Contributor

    Taking this off the critical list as well, since it's just a dependency of another one.

  8. Hixie
    removed
    customer: amplify
    severe: customer critical
    on Aug 28, 2019
  9. liyuqian
    added 2 commits that reference this issue on Sep 9, 2019

    Add a new package: measure (#31)

    db15561

    Measure iOS CPU/GPU percentage

    d055e77

  10. 14 remaining items

  11. liyuqian
    modified the milestones: August 2020, December 2020 on Jan 18, 2020

  12. liyuqian commented on Jan 18, 2020

    @liyuqian
    liyuqian
    on Jan 18, 2020
    ContributorAuthor

    This is currently blocked by #45435 on iOS. We'll also need to do some work to enable the measurement on Android.

  13. liyuqian
    added
    perf: energyPerformance issues related to energy use (power, watts)
    on Mar 6, 2020
  14. liyuqian
    removed their assignment
    on Apr 6, 2020
  15. kf6gpe
    added
    P1High-priority issues at the top of the work list
    on May 29, 2020

  16. kf6gpe commented on Aug 24, 2020

    @kf6gpe
    kf6gpe
    on Aug 24, 2020
    Contributor

    @liyuqian Blocking bug is closed. Should we get back to this now?

  17. liyuqian commented on Aug 24, 2020

    @liyuqian
    liyuqian
    on Aug 24, 2020
    ContributorAuthor

    Yes, this is done for iOS. We discussed the Android side of work several days ago and concluded that no one has the bandwidth to tackle it in Q3. We'll revisit it in Q4 OKR planning.

  18. kf6gpe commented on Aug 31, 2020

    @kf6gpe
    kf6gpe
    on Aug 31, 2020
    Contributor

    Downgrading to a P4 until we finish Q4 planning and know if this landed on the plate.

  19. kf6gpe
    added
    P2Important issues not at the top of the work list
    and removed
    P1High-priority issues at the top of the work list
    on Aug 31, 2020

  20. liyuqian commented on Sep 24, 2020

    @liyuqian
    liyuqian
    on Sep 24, 2020
    ContributorAuthor

    #61567 tracks the Android side of work. I'm going to close this and continue our future discussions in #61567

  21. liyuqian
    closed this as completedon Sep 24, 2020

  22. github-actions commented on Aug 12, 2021

    @github-actions
    github-actionsbot
    on Aug 12, 2021

    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.

  23. github-actions
    locked as resolved and limited conversation to collaborators on Aug 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)customer: crowdAffects or could affect many people, though not necessarily a specific customer.engineflutter/engine related. See also e: labels.perf: energyPerformance issues related to energy use (power, watts)

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions