microsoft / microsoft/winget-cli

"winget list --name xy" executes (VERY) SLOW when using broad filter (for the first time?)

Open
#4,701 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Performance Issue-Bug
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Brief description of your issue

when I execute "winget list" I do get a result with 376 entries. This command takes apr. 2.5 sec to execute and show.

when I execute "winget list --name My" I do get 4 lines and it takes apr. 4.5 sec.

when I execute "winget list --name Mi" I do get 134 lines (all containing Microsoft ;-) ). This took about 2:40 minutes to show the first time I called it. After the successful call the same command takes now apr. 10 sec. (Also if executed in new Command window)

when executing "winget list --name A" I never was able to get any result until now....

Note: the spinning '|' indicator in all cases stops after some seconds and a 'normal blinking console cursor' is shown for the rest of the time.

Steps to reproduce
  • open normal cmd window with 'run as admin'.
  • type "winget list --name A"
Expected behavior

there should a result be presented after some decent time.

Actual behavior

the example from "steps to reproduce" never gave any results after keeping the command window open for more than 15 minutes....

Environment
Windows-Paket-Manager v1.8.1911
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.22631.3880
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.23.1911.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start by reproducing winget list --name A and compare it with the reported timings for broad and narrow filters on the stated Windows environment; done means broad name filters return results in a reasonable, consistent time rather than hanging for 15 minutes.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
43/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.