Skip to content

Audit performance of the various DevTools screens and components #5091

Description

@bkonyi

A common concern raised by some Dash engineers is that DevTools often feels slower than existing tooling in Observatory.

Some examples of scenarios with poor performance:

  • Opening DevTools while connecting to a CLI application automatically fetches and loads a timeline, locking up the UI thread until the timeline is fetched and processed
  • Poor performance when creating filtered CPU profiles

Performance of the various tools should be audited to ensure that current power users of Observatory do not experience a degradation of their development workflows.

This is a blocker for deprecating and removing Observatory from the Dart SDK.

cc @a-siva @jacob314

Activity

  1. kenzieschmoll commented on Mar 10, 2023

    @kenzieschmoll
    Member

    Another possible performance optimization: stop copying data for flat tables https://github.com/flutter/devtools/pull/5384/files#r1132405605

  2. kenzieschmoll commented on Apr 21, 2023

    @kenzieschmoll
    Member

    Opening DevTools while connecting to a CLI application automatically fetches and loads a timeline, locking up the UI thread until the timeline is fetched and processed

    @bkonyi is this still an issue with the new perfetto integration? If it's not a problem now, there may not be a reason to invest in creating an "index" screen for cli apps.

  3. bkonyi commented on Apr 26, 2023

    @bkonyi
    ContributorAuthor

    I'm personally content with the landing page performance as Perfetto doesn't seem to cause the UI thread to jank when loading the initial timeline like it did before, so users can still switch to another tab while the timeline is being processed. However, I do feel having an overview landing page could be useful, particularly in VM developer mode (cc @a-siva for his thoughts), but that can be pulled out into its own issue.

    I think we can close this issue once #5703 is resolved.

  4. kenzieschmoll commented on Apr 26, 2023

    @kenzieschmoll
    Member

    Landing screen is tracked here: #4603. Since #5703 has been broken out into smaller tracking issues and is a meta tracking issue for all the smaller items, I'm going to let that work be tracked there. I will close this out, and I will add the appropriate labels to the other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions