async versions of slow libuv calls?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
e.g. child_process.spawn and os.cpus() can be very slow calls that cause lag on the main thread. Would it make sense to perform async versions of these calls that run on a worker thread?
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 by investigating the child_process.spawn and os.cpus() entry points and how their current libuv calls run on the main thread. Determine the scope and API design for worker-thread-based asynchronous versions, then verify that the proposed calls no longer cause main-thread lag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100