microsoft / microsoft/vscode-js-profile-visualizer

No support for Multi-threading? Inaccurate CPU usage with threaded application.

Open
#76 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
158
Forks
30
Avg merge
22h 29m
Merged PRs (30d)
8

Description

CPU usage is shown 100% even when,

  • Nodejs single-threaded app is using only one core fully.
  • Nodejs threaded app is using any number cores fully.
  • there are clear ups and down shown on the graph.

Attaching 2 screenshots showing different cases,

  1. Main nodejs app with 1 extra worker thread doing CPU intensive work.
    See, at OS level node is registering 20% CPU load. (which is close to fully utilizing one core of a quad core CPU)

Screenshot_2

  1. Main nodejs app with 7 extra worker threads doing CPU intensive work.
    At OS, level node is registering 89% CPU load.

Screenshot_3

In both cases, CPU usage is shown 100%. Secondly, the graph itself has ups and downs which is not reflected in the CPU usage number.

Also is it possible to get total RAM usage? In the second screenshot, heap is 125 MB whereas at system level, node is occupying 9.5 GBs of RAM.

Contributor guide

No contributing guide indexed for this repository

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 files, tests, or entry points are named. Start by reproducing the reported single-threaded and worker-thread CPU cases and comparing the visualizer's CPU and heap values with the operating-system measurements; done means the displayed CPU usage follows actual utilization and total RAM usage is addressed or clearly scoped.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.