sindresorhus/fkill

Is there any change to optimize the processing time?

Open

#25 opened on Aug 6, 2018

View on GitHub
 (12 comments) (0 reactions) (0 assignees)JavaScript (794 stars) (76 forks)user submission
:dollar: Funded on Issuehuntenhancementhelp wanted

Description

I need to kill the process tree in 5 seconds. However, I found that the code will run almost 10+ seconds before returned. Any suggestions? Thanks.

const fkill = require('fkill');
...
await fkill(pid, {"force": true, "tree": true}); // It takes longer than expected

Backers (Total: $8.00)

Submitted pull Requests

Become a backer now!

Or submit a pull request to get the deposits!

Tips

Contributor guide

Tech stack
javascriptnodejs
Domain
cli
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.js fundamentalsprocess managementasync/await
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the current implementation of the fkill function, likely in index.js, to identify sequential process kills. Consider using parallel kills or more efficient system calls. Review the linked pull requests on Issuehunt for potential approaches. Ensure cross platform compatibility when optimizing.