Investigate increasing open file limit
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
A follow-on from https://github.com/nodejs/nodejs.org/issues/5184 and https://github.com/nodejs/nodejs.org/issues/5149, we should look at increasing the number of files that NGINX can have open at any one time.
This could either be done by increasing the system ulimit, or by setting worker_rlimit_nofile in NGINX.
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 reviewing the linked issues 5184 and 5149, then inspect the NGINX deployment and its system file-descriptor limits. Compare increasing the system ulimit with setting NGINX's worker_rlimit_nofile; done means selecting and applying a verified approach that increases the number of files NGINX can keep open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, nginx
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100