Sizing recommendation to configure Traffic Flow Solution pack.
search cancel

Sizing recommendation to configure Traffic Flow Solution pack.

book

Article ID: 386594

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

CPU/Memory/Disk Recommendations

 

Environment

Watch4net / MnR - 7.x 

Resolution

Note: A traffic flow Event Processing Manager (EPM) can handle approximately 10k flows per second. The following are the recommendations for 10k flows per second:

  1. Configure 8GB of JVM heap memory to process incoming flow data by setting 'memory.max' to '8192' in the <BASEDIR>/APG/Event-Processing/Event-Processing-Manager/generic-traffic-flow/conf/unix-service.properties file.
  2. Ensure a CPU speed of 3GHz and 4 vCPUs for each traffic flow collector (EPM), backend (Elasticsearch server).
  3. Ensure a Memory 32GB for each traffic flow collector (EPM), backend (Elasticsearch server).
  4. Allocate 1.2TB of dedicated storage to retain the data for 365 days. It is suggested to setup ElasticSearch in a cluster mode, ensuring each node in the cluster honors sizing as mentioned in point 2,3 and 4.
  5. Run one traffic flow EPM service per collector server.
Powered by Wolken Software