1. vRule Engine deploys a number of worker threads to handle Application data traffic. The default value is typically configured to two threads. Each worker thread requires 1 vCPU

  2. However, if an Application requires more throughput, then it is recommended to increase the number of worker threads in vRule

  3. The number of worker threads and memory can be configured by executing the commands below:

    1. Modify the number of threads:

      1. vsp-cli config ae edit numWorker <1-16> --persist


    2. Disable auto-scaling feature:

      1. vsp-cli config ae edit autoscaling false


  4. When the application throughput requirement is more than the supported value, it creates a congestion in the vRule Engine and as a result, packets are dropped by vRule’s flow controls. The number of packets dropped are logged in the vRule stats file

  5. vRule stats are available in the file: /vspstats/vrule/vrule_stats. The below diagram depicts a part of vRule stats file

    Picture 15

  6. If drop count increases continuously, then it is a clear indication that more worker threads are needed



      There should be a continuous increase in the drop count


  7. Received M indicates the accumulated number of data plane messages. The rate of increase of these messages indicates the overall throughput rate at which vRule Engine is processing data packets

  8. The average packet size and throughput can also be obtained from the VSP CMS dashboard