Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add resource requirements topic #6001

Closed
wants to merge 3 commits into from
Closed

Add resource requirements topic #6001

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6f5d4f8
Initial draft for sizing info
clayton-cornell Dec 18, 2023
39d04b2
Update topic name and structure
clayton-cornell Dec 18, 2023
5d5268e
Update meta data
clayton-cornell Dec 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
69 changes: 69 additions & 0 deletions docs/sources/flow/requirements/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
---
aliases:
- /docs/grafana-cloud/agent/flow/requirements
- /docs/grafana-cloud/send-data/agent/flow/requirements
canonical: https://grafana.com/docs/agent/latest/flow/requirements/
description: Resource requirements
menuTitle: Sizing
title: Resource requirements
weight: 100
---

# Resource requirements

Capacity planning for {{< param "PRODUCT_NAME" >}} is a very important step in the deployment process. The sizing and capacity requirements for {{< param "PRODUCT_NAME" >}} depends on your specific environment, and the workload you have. Understanding the minimum hardware requirements for Grafana Agent Flow XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx

## Baseline

The following values define the baseline for estimating the resource requirements for {{< param "PRODUCT_NAME" >}}. These values provide a starting point for your deployment requirements.

| Data point | Size | Throughput |
|------------|---------|------------|
| Metrics | XXXXXXX | XXXXXXX |
| Events | XXXXXXX | XXXXXXX |
| Logs | XXXXXXX | XXXXXXX |
| Traces | XXXXXXX | XXXXXXX |

A metrics series is active if it continuously has new data points appended to it. A metric series become inactive if they haven't received any new samples since the last WAL truncation interval.

## Test environment

Info about Agent version, software/OS, hardware etc. Definition of what a vCPU is?

Does it make any difference running on Linux, Windows, OSX, etc.?

### Test results for 14,000,000 to 16,000,000 metric series

| vCPU cores | Memory | Disk I/O | Disk space | Network |
|------------|----------------|-------------------------------------------------|------------------| ------- |
| 1.5 to 2.2 | 81 GB to 88 GB | 0.7%, with periodic spikes to 6%-8% for the WAL | 2.7 GB to 7.4 GB | XXXXXX |

### Test results for 650,000 to 800,000 metric series

| vCPU cores | Memory | Disk I/O | Disk space | Network |
|------------|------------------|------------------------------------------------|------------------| ------- |
| 0.1 to 0.2 | 3.9 GB to 5.7 GB | 0.3%, with periodic spikes to 0.4% for the WAL | 230 MB to 410 MB | XXXXXX |

## Recommendations

Intro covering general recommendations.

### CPUs

Info about vCPUs for common use cases. For example X vCPUs when scraping some measurable number of metrics and sending over remote_write.

### Memory

Info about memory/RAM for common use cases. For example X GB RAM when scraping some measurable number of metrics and sending over remote_write.

### Disk

Info about disk space for common use cases. For example X GB of disk space when scraping some measurable number of metrics and sending over remote_write.

### Network

Info about network bandwidth for common use cases. For example X MBps when scraping some measurable number of metrics and sending over remote_write.

## Clustering requirements

Text