> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/deployment/stream/stream-sizing.md).

# Stream sizing

Sizing guidelines for Stream VMs and M-Series appliances.

When considering sizing for Stream it is important to understand that the traffic mix at customer sites varies widely. Some customers have traffic mixes that skew towards larger flows (think file transfers), and some will skew towards smaller flows. Performance will be lower when the traffic mix skews towards smaller flows as there will be more metadata to process. The below are guidelines for average traffic mixes and should not be considered absolute. Throughput refers to the amount of traffic observed by Sensors that forward metadata to the Vectra platform.

**Virtual Appliances:**

<table><thead><tr><th width="134.9375" align="center">Hypervisor / Cloud</th><th width="179.2890625" align="center">VM Type</th><th width="92.26953125" align="center">Cores</th><th width="105.6484375" align="center">Memory</th><th width="98.7421875" align="center">Storage</th><th width="141.7578125" align="center">~ Performance</th></tr></thead><tbody><tr><td align="center">VMware</td><td align="center">vSphere 6.5 or later</td><td align="center">2</td><td align="center">8 GB</td><td align="center">100 GB</td><td align="center">Up to 2.5 Gbps</td></tr><tr><td align="center">VMware</td><td align="center">vSphere 6.5 or later</td><td align="center">4</td><td align="center">8 GB</td><td align="center">150 GB</td><td align="center">2.5 to 5 Gbps</td></tr><tr><td align="center">VMware</td><td align="center">vSphere 6.5 or later</td><td align="center">8</td><td align="center">16 GB</td><td align="center">150 GB</td><td align="center">5 to 10 Gbps</td></tr><tr><td align="center">VMware</td><td align="center">vSphere 6.5 or later</td><td align="center">16</td><td align="center">64 GB</td><td align="center">150 GB</td><td align="center">10 to 20 Gbps</td></tr><tr><td align="center">Hyper-V</td><td align="center">Windows Server 2016 w/ HW v8 or higher</td><td align="center">2</td><td align="center">8 GB</td><td align="center">100 GB</td><td align="center">Up to 2.5 Gbps</td></tr><tr><td align="center">Hyper-V</td><td align="center">Windows Server 2016 w/ HW v8 or higher</td><td align="center">4</td><td align="center">8 GB</td><td align="center">150 GB</td><td align="center">2.5 to 5 Gbps</td></tr><tr><td align="center">Hyper-V</td><td align="center">Windows Server 2016 w/ HW v8 or higher</td><td align="center">8</td><td align="center">16 GB</td><td align="center">150 GB</td><td align="center">5 to 10 Gbps</td></tr><tr><td align="center">Hyper-V</td><td align="center">Windows Server 2016 w/ HW v8 or higher</td><td align="center">16</td><td align="center">64 GB</td><td align="center">500 GB</td><td align="center">10 to 20 Gbps</td></tr><tr><td align="center">KVM</td><td align="center">Proxmox, Libvrt, or other VMM</td><td align="center">2</td><td align="center">8 GB</td><td align="center">100 GB</td><td align="center">Up to 2.5 Gbps</td></tr><tr><td align="center">KVM</td><td align="center">Proxmox, Libvrt, or other VMM</td><td align="center">4</td><td align="center">8 GB</td><td align="center">150 GB</td><td align="center">2.5 to 5 Gbps</td></tr><tr><td align="center">KVM</td><td align="center">Proxmox, Libvrt, or other VMM</td><td align="center">8</td><td align="center">16GB</td><td align="center">150 GB</td><td align="center">5 to 10 Gbps</td></tr><tr><td align="center">KVM</td><td align="center">Proxmox, Libvrt, or other VMM</td><td align="center">16</td><td align="center">64 GB</td><td align="center">500 GB</td><td align="center">10 to 20 Gbps</td></tr><tr><td align="center">AWS</td><td align="center">c5.xlarge</td><td align="center">4</td><td align="center">8 GB</td><td align="center">50 GB</td><td align="center">Up to 5 Gbps</td></tr><tr><td align="center">AWS</td><td align="center">c5.2xlarge</td><td align="center">8</td><td align="center">16 GB</td><td align="center">50 GB</td><td align="center">5 to 10 Gbps</td></tr><tr><td align="center">AWS</td><td align="center">c5.4xlarge</td><td align="center">16</td><td align="center">32 GB</td><td align="center">50 GB</td><td align="center">10 to 20 Gbps</td></tr><tr><td align="center">Azure</td><td align="center">Standard_DS4_v2</td><td align="center">8</td><td align="center">28 GB</td><td align="center">50 GB</td><td align="center">Up to 10 Gbps</td></tr><tr><td align="center">Azure</td><td align="center">Standard_D8ds_v5</td><td align="center">8</td><td align="center">32 GB</td><td align="center">50 GB</td><td align="center">Up to 10 Gbps</td></tr><tr><td align="center">Azure</td><td align="center">Standard_DS5_v2</td><td align="center">16</td><td align="center">56 GB</td><td align="center">50 GB</td><td align="center">10 to 20 Gbps</td></tr><tr><td align="center">Azure</td><td align="center">Standard_D16ds_v5</td><td align="center">16</td><td align="center">64 GB</td><td align="center">50 GB</td><td align="center">10 to 20 Gbps</td></tr><tr><td align="center">GCP</td><td align="center">e2-standard-4</td><td align="center">4</td><td align="center">16 GB</td><td align="center">50 GB</td><td align="center">Up to 5 Gbps</td></tr><tr><td align="center">GCP</td><td align="center">e2-standard-8</td><td align="center">8</td><td align="center">32 GB</td><td align="center">50 GB</td><td align="center">5 to 10 Gbps</td></tr><tr><td align="center">GCP</td><td align="center">e2-standard-16</td><td align="center">16</td><td align="center">64 GB</td><td align="center">50 GB</td><td align="center">10 to 20 Gbps</td></tr></tbody></table>

**Vectra M Series Physical Appliances:**

The M47 physical appliances can support up to \~100 Gbps of throughput.

{% hint style="info" %}
**Please Note:**

* Contact your account team or Vectra support for guidance on special situations, abnormal traffic mixes, or throughput needs outside of what is documented above.
* Vectra recommends that Stream VMs are configured to use storage local to the hypervisor and are not stored on a SAN. Stream VMs require extremely high throughput from their disk storage and this throughput cannot normally be sustained by SAN systems without impact to other SAN users.
* Please see [VMware deployment details and considerations](https://docs.vectra.ai/deployment/ndr-virtual-cloud-appliances/vmware-vsensor/vmware-deployment-details-and-considerations.md) for guidance on supported CPUs, storage/SANs, networking requirements, vMotion, Enhanced vMotion compatibility, and unsupported hypervisors. While Sensor and VMware specific, this article applies to Stream VMs as well. The general guidance in the article also applies to Hyper-V and KVM deployments.
  {% endhint %}


---

# 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.vectra.ai/deployment/stream/stream-sizing.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.
