# 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: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.licensespring.com/floating-server/floating-server-v1/deployment-methods/configuration/storage-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.