microsoft / microsoft/winget-cli
DSC Schema V3 is extremely slow when referring to V2 resources
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
DSC Resource, WinGet CLI
Relevant command(s)
winget configure
Brief description of your issue
I updated one of my configuration files to the v3 schema. It took several times as long to run winget dsc test <config> using the V3 schema with V2 resources as it did when using the V2 schema
Steps to reproduce
Convert a V2 Schema Config to a V3 Schema Config
Expected behavior
Performance is less significantly impacted
Actual behavior
There is a significant performance impact. It take 4-5 times as long, perhaps even longer
Environment
.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the DSC Resource and WinGet CLI areas, then reproduce the report by running winget dsc test <config> on equivalent V2 and V3 schema configurations that use V2 resources. Trace the V3 path and compare its resource handling with V2. Done means the significant performance gap is reduced and the comparison is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100