> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/floating-server/floating-server-v1/deployment-methods/configuration/storage-requirements.md).

# Storage Requirements

The Floating Server is designed with a light footprint in mind, ensuring that it remains efficient and unobtrusive in various operational environments.

{% stepper %}
{% step %}

### Badger Database

The Badger database starts with a pre-configured allocation of 102 megabytes, optimized for minimal impact while providing ample storage for typical usage. This size can accommodate the standard data load with significant room for growth, although exceeding this capacity is rare. Typically, surpassing the 100-megabyte threshold would require the storage of over 100,000 data points, a scenario unlikely under normal operational conditions.
{% endstep %}

{% step %}

### Redis Database

The Redis database starts with a negligible initial footprint and is designed to scale efficiently with data addition. Extensive testing has demonstrated that even with up to 10,000 data points, the database consumes less than 5 megabytes of storage. This consistent performance affirms our expectation that the Redis database will comfortably remain well under 100 megabytes for standard usage, ensuring optimal efficiency and resource management.
{% endstep %}
{% endstepper %}


---

# 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.licensespring.com/floating-server/floating-server-v1/deployment-methods/configuration/storage-requirements.md?ask=<question>&goal=<user_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.