Skip to content

Running Extensions: sort slowest ⟶ fastest#103336

Merged
alexdima merged 1 commit intomicrosoft:masterfrom
bmalehorn:bm/profile-sort
Aug 30, 2020
Merged

Running Extensions: sort slowest ⟶ fastest#103336
alexdima merged 1 commit intomicrosoft:masterfrom
bmalehorn:bm/profile-sort

Conversation

@bmalehorn
Copy link
Contributor

Before, the > Developer: Show Running Extensions page was sorted by:

  1. whether or not they were unresponsive
  2. name identifier

In Windows Task Manager, Mac System Monitor, and top, the default shows the worst offenders. But the running extensions view is sorted by name identifier. This makes it difficult to answer the question "what's slowing my system down?"

image

Now, extensions are sorted by:

  1. whether or not they were unresponsive
  2. last profile time
  3. activation time
  4. name identifier

In practice this means the first time you open running extensions, it will be sorted by activation time:

image

When you profile extensions, it will be sorted by profile time:

image

I'm not sure if this is the absolute best way to do this - maybe users should be able to choose what to sort by - but it should make it a lot easier to find slow extensions quickly.

@bmalehorn bmalehorn changed the title Running Extensions: sort slowest → fastest Running Extensions: sort slowest ⟶ fastest Jul 25, 2020
Before, extensions were sorted by:

1. whether or not they were unresponsive
2. name identifier

This made it difficult to answer the question "which extensions are slowing me down"?

Now, extensions are sorted by:

1. whether or not they were unresponsive
2. last profile time
3. activation time
4. name identifier

In practice this means the first time you open running extensions, it will be sorted by activation time. When you profile extensions, it will be sorted by the profile time.
@alexdima
Copy link
Member

Thank you!

@alexdima alexdima merged commit 70782eb into microsoft:master Aug 30, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Oct 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants