> For the complete documentation index, see [llms.txt](https://docs.blusapphire.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blusapphire.io/release-6.0/03_datastreamer/getting-started.md).

# Getting Started

## System Requirements**:**

The Data Pipeline Manager (DPM) can be deployed both physically (or) virtually with the below hardware requirements. DPM will automatically take advantage of the resources available.

| **Minimum**                                           | **Recommended**                                        |
| ----------------------------------------------------- | ------------------------------------------------------ |
| 4 vCPUs, 8GB RAM, 125GB SSD of primary storage, 1 NIC | 8 vCPUs, 16GB RAM, 250GB SSD of primary storage, 1 NIC |

*1 vCPU = 1 ARM physical CPU or 0.5 Intel physical CPU with hyperthreading*.

#### **Memory**

As a basic starting point, we advise 2 GiB of memory per vCPU. Because of in-memory batching and buffering, memory utilization rises as the number of destinations increases. If you have several destinations, you might want to think about using disk buffers or upgrading the memory. Since disk buffers are slower, we advise boosting memory wherever it is practical.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.blusapphire.io/release-6.0/03_datastreamer/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.