vSTREAM Embedded resource usage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
| | ||
(*) vSTREAM Embedded has the ability to capture and store a small amount of data packets on the host. Those packets are kept in RAM and not stored on the hard disk of the host. In this case, memory requirements will increase | <span style="font-size:smaller;">(*) vSTREAM Embedded has the ability to capture and store a small amount of data packets on the host. Those packets are kept in RAM and not stored on the hard disk of the host. In this case, memory requirements will increase</span> | ||
Revision as of 07:16, 9 May 2019
Introduction
 | vSTREAM Embedded and vSTREAM Standalone are two different products. This article only applies to vSTREAM Embedded. |
vSTREAM Embedded runs as a service on Linux and as background application on a Windows. Consequently, vSTREAM Embedded is using a small amount of host resources. vSTREAM Embedded has the ability to capture and store a small amount of data packets on the host.
Solution
 | Do not install vSTREAM Embedded on a host with less than two CPU and less than two GB of RAM. |
- vSTREAM Embedded uses up to an equivalent of 100% of a single CPU. The vSTREAM Embedded processes may appear on two CPUs, but the total usage will be less than 100% of a single CPU
- vSTREAM Embedded requires 1 GB of free RAM and will not exceed this amount*
- vSTREAM Embedded uses a maximum of 500 MB of local storage
(*) vSTREAM Embedded has the ability to capture and store a small amount of data packets on the host. Those packets are kept in RAM and not stored on the hard disk of the host. In this case, memory requirements will increase