In this section:

Benchmarking Setup

The two test beds used to collect benchmarking data are depicted below.

  • 1:1 HA SBC-CE on AWS.
  • Test tools: Two Pktarts on AWS, one for UAC and other one for UAS.

 

Benchmarking Setup

 

 

Notes
  • Benchmarking is done on an SBC HA with HFE. Call flow includes nine signaling messages with media. Calls tested Public to Private.
  • The SBC HA with HFE and PKTART are running on a default tenant.
  • PKTart Tool flavor used is c5.2xlarge instance type for benchmarking all the SBC with HFE instances, except for c5.4xlarge. For c5.4xlarge, Pktart Instance flavor is same as that of SBC.
  • The performance test was performed for 1 hour.
  • Benchmarking results vary based on the AWS network.
  • 95 percentile data is specified in pktloss unless specified.
  • The setup for TLS-SRTP:: UAC-->ADAP-->DUT-->UAS.

Benchmarking Data – HFE With HA SBC

Volume Type io1

Click to view table...

Maximum Initial (challenged) REGISTER Rate with Background Load

Instance Type: C5.4X Large HA Mode

Protocol

Initial SIP 
Registration/Sec

Number of 
Subscribers

Interval of Refresh
REGISTER (Seconds)


SIP Calls/Sec

UDP

700

60,000

30

30

700

120,000

60

30

TCP

680

256,000

300

30

TLS

680

256,000

300

30

 

SIP Session and Registration Capacity Limits

SIP Session and Registration Capacity Limits Instance Type: C5.4X Large HA Mode

Protocol

Sessions

SIP Calls/Sec

Call Hold
(seconds)

Interval of Refresh
REGISTER (Seconds)

Subscribers

Registration/Sec

UDP

3,600

60

60

60

120,000

500

3,600

60

60

30

60,000

500

TCP

3,600

60

60

300

256,000

500

In the current implementation, the send and receive buffer size for TCP packets is restricted to 64 kilobytes. Due to this limitation, the SBC cannot handle traffic where the product of the TCP packet size (measured in kilobytes) and the processor rate (measured in cycles per second) exceeds 64. For example, if the packet size is 3 kilobytes and the processor rate is 25 cycles per second, the product is 75, which is greater than the TCP buffer size. If the TCP buffer overflows, the SBC resets the connection. This is particularly important when the packet sizes are large, as in case of packets containing the INFO header that bloats the packet sizes.