> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/configuration/bindplane/increase-max-open-files-limit.md).
# Increase Max Open Files Limit
### File Handles
Linux processes are limited to 1024 open file handles by default. Bindplane's file handles consist of network connections and open files.
You can use the following calculation to determine the estimated number of open file handles by Bindplane: `500 + (2 * Number of collectors)`. For example, if you have 200 collectors, you can expect to see up to 900 file handles.
The number of file handles will differ between Bindplane configurations. For example, when using PostgreSQL as a storage backend, Bindplane will use up to 100 network connections by default. When using Bolt Store, Bindplane will consume one file handle.
Using 500 file handles as a base allows the calculation to account for all Bindplane configurations.
### Configure Max File Handles
Bindplane relies on the systemd option `LimitNOFILE` to limit the maximum number of open files. By default, this value is `55000`.
You can configure the max open files by using a [Systemd override](https://wiki.archlinux.org/title/systemd). Run the following command:
```bash
sudo systemctl edit bindplane
```
Modify the unit file's override to look like this:
After saving the file, you can reload systemd and restart Bindplane.
```bash
sudo systemctl daemon-reload
sudo systemctl restart bindplane
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bindplane.com/configuration/bindplane/increase-max-open-files-limit.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
