microsoft / microsoft/vscode-windows-process-tree
More metrics
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 94
- Forks
- 29
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 4
Description
Hi!
This is a follow up on https://github.com/simonepri/pidtree/issues/6. I'm the original author of pidusage (written for pm2 back in the days). pidusage is a library that facilitate the access to cpu and memory usage, for a given pid, being cross-platform.
For windows, we're spawning wmic.exe to get the following metrics:
'CreationDate,KernelModeTime,ParentProcessId,ProcessId,UserModeTime,WorkingSetSize'
It works well but is god damn slow!
Would it be possible to add these additional metrics in this module? I'm really not familiar with windows nor with C++ programming on windows or I'd definitely do it myself. This would be a huge improvement for windows users that use pidusage to get cross-platform metrics.
Thanks!
Contributor guide
No contributing guide indexed for this repository
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 with issue 6 and the repository’s Windows process-tree entry point, then compare the current metrics with the WMIC fields listed here. Done means exposing those additional metrics while addressing the slow Windows path and preserving cross-platform process-tree behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100