vSTREAM Embedded resource usage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
== Introduction == | == Introduction == | ||
| |||
== | {{#invoke:Message box|ambox |type=content|text=vSTREAM Embedded and vSTREAM Standalone are two different products. This article only applies to vSTREAM Embedded.}} | ||
| | ||
vSTREAM Embedded runs as a service on a Linux host and a background application on a Windows host. Consequently, vSTREAM Embedded is using the host resources. | |||
== Solution == | |||
| | ||
Revision as of 07:10, 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 a Linux host and a background application on a Windows host. Consequently, vSTREAM Embedded is using the host resources.
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