1. Home
  2. Getting Started
  3. Performance Guide for the OmniCenter Virtual Appliance
  1. Home
  2. Administrator Reference
  3. Performance Guide for the OmniCenter Virtual Appliance

Performance Guide for the OmniCenter Virtual Appliance


Netreo’s OmniCenter product is deployed as a virtual appliance (VA), typically hosted within the customer’s virtualization environment. All of OmniCenter functions and features are fully supported when deployed as a VA.

These performance guidelines will assist customers in allocating the appropriate amount of resources to an OmniCenter VA (OCVA). This is not a comprehensive guide, and is intended only to give a general idea of the performance levels that can be expected based on the amount of resources allocated. For additional guidance when setting up your OCVA, please feel free to contact Netreo technical support for customized advice.

OmniCenter is installed in virtual environments by deploying a machine image. Do not provision a new guest before deploying the image.

OmniCenter uses a Linux-based core for basic hardware support and OS functions, and is designed to make maximum use of the available hardware resources. For this reason, Netreo does not recommend deploying an OCVA in virtual environments that are heavily oversubscribed, as performance may be adversely affected.

OmniCenter can be configured with many optional features such as application response time (ART) monitoring, email and exchange monitoring, traffic flow analysis, and IP Telephony management. OmniCenter deployments using these features (especially traffic flow and IP Telephony) will generally require more resources for a given size of environment. OmniCenter can be configured in excess of these guidelines up to the limit of your software device license.

You should also consider carefully the merits of monitoring your VM environment from a guest inside the environment, as a virtual environment outage could disable OmniCenter and prevent you from being alerted. If your VM environment is not highly redundant and stable, Netreo recommends the use of dedicated hardware.

General Requirements

  • VMware vSphere 5.0 or later, Microsoft Hyper-V or Scale HC3 hypervisor.
  • Intel or AMD processors >= 2.0 GHz with hardware virtualization support.
  • 8GB RAM minimum.
  • Disk storage requirements may vary by environment, the values listed below should cover 95% of implementations.
  • SSD storage is highly preferred, especially for environments over 1000 devices. SSD-based storage is mandatory for environments over 2,500 devices or environments over 300 devices where Flow technologies (NetFlow, sFlow, IPFIX) are in use. NFS-based datastores are not supported.
  • Datastore latency is a significant factor. Netreo recommends < 5ms write latency and < 10ms total latency for optimal performance.

Due to constant database updates during data collection, most environments will have a 90%-write, 10%-read disk I/O profile—which may require special configuration of your datastore for optimal performance. OmniCenter is extremely disk write intensive and is not tolerant of high latency or unstable storage environments. If you have concerns about your storage performance or stability, dedicated hardware is recommended.

Scalability Guidelines

These recommendations are based on Netreo best practices and an average customer deployment. Customers with specialized environments that require large amounts of monitoring, rapid monitoring intervals, large numbers of simultaneous users, or large volumes of IPTel call data or flow data will require more resources.

These recommendations are also based on hundreds of hours of testing and real-world experience with diverse customer environments across many industries. While provisioning fewer resources may work adequately for some customers, our experience has shown that under-provisioning can lead to unsatisfactory performance and reduced reliability. The advantage of a VM environment is that even if over-provisioned for a specific environment, virtual hypervisors will happily share any unused resources (including disk, which we recommend be thin-provisioned so it is only used if and when needed) with other VMs. We therefore do not recommend provisioning less than the prescribed amount of CPUs, memory and disk space.

Number of Devices Recommended Configuration
Less than 100 4 vCPU
100GB Disk space11
Up to 300 8 vCPU
100GB Disk space12
Up to 1,000 16 vCPU
200GB Disk space13 (SSD strongly recommended)
Up to 3,000 32 vCPU
600GB Disk space14 (SSD required)
Up to 5,000 64 vCPU
128G RAM
1TB Disk space15 (SSD required)
More than 5,000 Dedicated hardware recommended
Updated on April 12, 2019

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Reply