WICG / WICG/cpu-performance

Difference from navigator.hardwareConcurrency

Open Beginner friendly
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
37
Forks
7
PR merge metrics
No merged PRs in 30d

Description

CPU Performance API is conceptually very similar to Hardware Concurrency API. The CPU Performance API specification defines the algorithm Computing Performance Tier Value in terms of "physical or logical" CPU cores, but in practice it appears that all implementations report the number of "logical" cores. Hardware Concurrency API explicitly states that it reports the number of "logical" CPU cores. Granted, the two APIs report different numbers, but it would be interesting to read a comparison between these APIs, since this topic is not covered by the explainer, to the best of my knowledge.

Previously, #1 discussed the correlation between CPU Performance API and CPU Performance API, with the conclusion being that the correlation between the number of CPU cores and number of GBs of RAM is very weak. Explainer even explicitly mentions Device Memory API as a source of inspiration for this API.

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

Start by reading the CPU Performance API explainer and the linked Hardware Concurrency API specification, then compare how each API describes CPU cores and the values they expose. Add a clear comparison covering the reported core counts and their relationship; the work is done when the explainer addresses this distinction.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.