This article aims to help you anticipate better what resources utilization will be used by vRx's service
Understanding vRx Activity Modes:
After vRx is deployed on an asset, the service \ daemon resource consume will change according to it current operation. Lets start by covering the main operations executed by the service:
- Idle - If no operation is currently running on the asset.
- Scanning - During service startup and periodically, Topia's service will scan for any application changes, computer information (such as IP, groups, etc.) and more.
- Patching - During executing patches on the asset.
Resource Usage
Asset resource usage may vary according to many factors. We always recommended to reserve at least 10% of asset resources as a buffer for heavy tasks.
In the following table we would describe expected resource utilization on an asset:
| Windows | Linux / MacOS | |
|
Idle |
RAM: ~ 40MB - 100MB CPU: ~ 0% - 3% |
RAM: ~ 40MB - 100MB CPU: ~ 0%-3% |
| Scanning | RAM: ~ 100MB - 500MB CPU: 3% - 5% |
RAM: ~ 70MB - 400MB CPU: 3% - 5% |
| Patching | Scanning resources + Patch installer resources* | Scanning resources + Patch installer resources* |
* OS patches & Third Party installers require their own resources during execution. For more information on resources effect by installers, please refer to the software manufacture support website.
Patchless Protection
Enabling Patchless protection on an asset will cause some memory and CPU consumption overhead. You should take into account extended resource usage when enabling Patchless Protection on heavily loaded Assets.
Identify Service / Daemon Status
Information about the current tasks performed by the service are detailed in Topia's log files. For more information, please refer to "Topia Logs and Other Files" KB.