mafintosh / mafintosh/why-is-node-running
Document best practice to eliminate handles
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
Hey there! First of all, thank you a lot for this nice tool - this really shows how the internals of node keep the process alive.
I would love to know what exactly is the "best practice" in terms of closing handles.
I see there are `TLSWRAP`, `DNSCHANNEL`, `HTTPPARSER` and `TCPWRAP` open because I'm fetching data and open db connection.. So for a long-running process, that is ok, but what is the best practice to clean up? Does it hurt performance-wise to keep these handles open? I would think so.
But I have no idea how to stop them. A little bit of documentation how to deal with these would be very nice. Or at least a link to a guide :)
Thank you so much in advance.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by reading the repository's existing documentation and reviewing the Node.js handle types referenced in the issue: TLSWRAP, DNSCHANNEL, HTTPPARSER, and TCPWRAP. Done means documenting cleanup guidance and whether keeping these handles open affects long-running processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100