vSCOUT vSTREAM Embedded and vSTREAM Agent resource usage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
== Solution == | == Solution == | ||
| |||
{{#invoke:Message box|ambox |type=content|text=It is not recommended to run vSCOUT on a host with less than two CPU and two GB of RAM.}} | |||
| | ||
{{#invoke:Message box|ambox |type=content|text=If you are monitoring more than two interfaces, you must allocate at least two GB of memory to vSCOUT.}} | |||
| | ||
Revision as of 10:44, 21 June 2020
Introduction
Solution
 | It is not recommended to run vSCOUT on a host with less than two CPU and two GB of RAM. |
| If you are monitoring more than two interfaces, you must allocate at least two GB of memory to vSCOUT. |
vSCOUT runs as an application in a virtual or physical host. By default, vSCOUT uses the host’s system resources as follows:
- vSCOUT uses up to the equivalent of 100% of a single vCPU. vSCOUT processes may appear on up to two vCPUs, but the total usage will be less than 100% of a single vCPU.
- vSCOUT requires 1 GB of free RAM and will not exceed this amount
- vSCOUT uses a maximum of 500 MB of local storage