Skip to content

Profile and improve the performance of project searching and test discovery #5951

Closed

Description

@DanTup

Both of these can do a lot of disk access and can be slow if your disk I/O is not fast (for example because of Windows Defender or other AVs).

Improvements were made in #5934, but we can probably do better (for example by switching more disk I/O to async, or using the VS Code fs APIs).

Activity

  1. added this to the v3.132.0 milestone on Mar 2, 2026
  2. DanTup commented on Mar 16, 2026

    @DanTup
    MemberAuthor

    I re-profiled with the latest code, using the whole Flutter repo, opening the project, and triggering test discovery. For the whole capture of a few minutes (I'd updated, so there were no cached analysis results), the time spend in extension code was only hundreds of milliseconds.

    Image

    @FMorschel do you still have any projects that on the latest versions of the extension are slow for project search or test discovery? (Ideally tested with the AV off so the results aren't skewed by it, although the time with it on may still use a useful data point).

  3. DanTup commented on Mar 18, 2026

    @DanTup
    MemberAuthor

    Tentatively closing this, but we can re-open (or file a new issue with new profile traces) if things still seem slow.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions