microsoft / microsoft/SdnDiagnostics
Returning list of VMs and VMNetworkAdapters is slow
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 34
- Forks
- 6
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 5
Description
In systems where we have a heavy deployment of VMs, see often we hit a timeout exception when getting a list of VMs and VMNetworkAdapters from these hosts.
Look to generate the list of VMs and VMNetworkAdapters leveraging direct WMI calls or Cim Methods.
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
No file or test is named. Start by locating the code that collects lists of VMs and VMNetworkAdapters, then compare its current retrieval path with direct WMI calls or CIM methods. Done means the lists can be retrieved from hosts with heavy VM deployments without hitting the reported timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100