Skip to content

stock_animation_open_first_frame_average regressed  #42564

Closed

Description

@chinmaygarde

This looked fairly noisy before but never got back below the selected baseline after #42278.
Screen Shot 2019-10-11 at 8 59 26 PM

Activity

  1. chinmaygarde commented on Oct 12, 2019

    @chinmaygarde
    ContributorAuthor
  2. gspencergoog commented on Oct 12, 2019

    @gspencergoog
    Contributor

    Dang, looks like I just moved the regression from one benchmark to another. I might need some help finding something other ways to speed this up: I've already tried a lot of things.

  3. self-assigned this
    on Oct 12, 2019
  4. gspencergoog commented on Oct 15, 2019

    @gspencergoog
    Contributor

    OK, I'm officially stumped. I spent all day yesterday optimizing this code, and thought I had found a combination that almost eliminated this regression (1.3% instead of 5.1%), so I checked it in, but there has been no change in the benchmark.

    I have a spreadsheet where I tracked my changes and their effect, and it showed a clear improvement. I ran the benchmark 10x for each data point in my spreadsheet, and took the median (and the mean, just to sanity check). I'm running it on a Moto G4, set up the same as our benchmark devices.

    If I can't measure the impact of my changes, it's going to be pretty hard to optimize this...

  5. gspencergoog commented on Oct 15, 2019

    @gspencergoog
    Contributor

    After talking with others about this, I am going to rebaseline this as a fixed cost for the feature of keyboard shortcuts and focus traversal. I've done quite a lot of investigation and optimization of this code, and in reality there are probably more impactful optimizations that could be done in other areas of the code.

  6. 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.

  7. 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: performanceRelates to speed or footprint issues (see "perf:" labels)c: regressionIt was better in the past than it is now

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions