Call Capacity and Load Testing CURRI API

The default OVA is sized with capacity for most installations.

Default Capacity of Vmware Appliance

The OVA Appliance is generally sized for about 200 concurrent calls insepctions per second under 3ms round trip time, constant load (95th percentile) over ethernet. This will vary depending on your host CPU hardware, but is a good baseline for most installations.

Below is an actual load test sample, on version 0.8.1, in March 2024.

Host Environment

• Lenovo Mini Desktop I5-8500T (A laptop class CPU)
• Vmware 6.7
• Guest VM - Default Call Telemetry OVA - 2vCPU, 6GB RAM.

Client Details

• A 2019 Macbook Pro, conneced over ethernet, running a load testing script making API POST calls to the CURRI API.

TIP

You can scale the OVA to 8 vCPU and get load tested 600+ call inspections per second. HA Cluster load balancing acheives even higher numbers.

Load Testing your own Appliance

Below is a guide for load-testing the appliance and your hardware. Load Testing Guide

What happens if the appliance becomes overloaded?

If overloaded, the request from Cisco Callmanager may timeout. CUCM will timeout, this is configurable in Service Parameters. Calls will continue according to the ECC profile setting default - which defaults to allow calls. Most users will choose to allow the call if the API times out.

If you want to increase the capacity, just add more vCPU. The multi-core architecture supports 100 new call real-time policy inspections per vCPU Core per second while under 4ms round trip time.

Failover Concerns

The Enterprise HA Kubernetes option provides failover for the appliation and the PostgreSQL database. This is a 3 node cluster, and can handle a node failure. SQL is replicated across nodes. The extra nodes also increase overall capacity by load balancing.