In this section:
The performance of the SBC VM can be optimized if the call mix is provided while configuring the SBC SWe instance. A set of predefined call mixes are provided, these are called standard traffic profiles. Additionally, users can create custom traffic profiles, with a call mix that is more closely aligned with their specific deployment of SBC SWe.
The supported standard profiles are:
For deployments that require it, you can instantiate the SBC SWe in smaller-sized configurations that use limited memory and vCPU resources. However, the limited resources place some restrictions on capacity and capabilities. Refer to Small SBC SWe Deployment Characteristics and Performance Metrics for Small SBC SWe Configurations for more information.
Once the distribution of vCPUs is set, the SBC SWe overload behavior functions the same way as the hardware SBC (5000/7000 series).
This feature is applicable only when the vcpu is more than or equal to four.
When any standard profile is activated, the application automatically optimizes the vCPU usage of the SBC SWe VM for the activated profile.
Appropriate profiles are auto-configured on the D-SBC (microservices) based on the personality as follows:
On the D-SBC, the auto-configured profiles prevent reboot during instantiation.
If the call mix is different from one of those corresponding to the standard profiles, a custom profile can be created. You can create custom profiles based on the call mix requirements. While creating a custom profile, you must provide the call mix through CLI.
The estimated calls per second (cps) numbers are calculated based on certain conditions. The actual traffic may have a different number of signaling messages per call, message size, or call features for which the estimate could be inaccurate.