3.1.13. Maximum Capacity Specifications

This section shows maximum sizes and numbers of various objects/features that can be configured on a Virtual Service Router.

Note

The limits and timings in this article are only indicative and may vary with hardware capacity. Here is the reference platform that was used to produce the following numbers:

CPU	Intel® Xeon® Gold 6152 CPU @ 2.10GHz
Memory	48GB

Important

The timings reported in the following table are given when configuring objects all at once: starting with 0 configured objects and creating N new ones in a single <edit-config> or commit operation.

Configuring objects one by one (or incrementally) will be slower. Processing the difference between the current configuration and the increment takes more time, the bigger the configuration is.

However, this limitation only becomes significant when reaching the upper limits. For reasonably small setups, you can assume that the configuration time is linear with the number of configured objects.

Feature	Number of Objects	Configuration Time	Unconfiguration Time	Notes
Multiple logical VRF	50	2 s	2 s	1
Multiple logical VRF	500	10 s	30 s	1
Bridge	500	10 s	40 s	2, 3
Bridge	5000	60 s	600 s	2, 3
GRE	500	10 s	20 s	3
GRE	5000	100 s	250 s	3
IPv4 and IPv6 tunneling	500	5 s	20 s	3
IPv4 and IPv6 tunneling	5000	80 s	250 s	3
LAG	500	10 s	20 s	3
LAG	5000	100 s	300 s	3
Loopback	500	10 s	20 s
Loopback	5000	60 s	250 s
Static routes	500	5 s	2 s
Static routes	5000	30 s	10 s
SVTI	500	10 s	30 s	3
SVTI	5000	60 s	250 s	3
veth, XVRF	100	10 s	5 s	4
veth, XVRF	500	60 s	200 s	4
VLAN	500	15	25 s	3
VLAN	5000	150 s	250 s	3
VXLAN	500	15	25 s	3
VXLAN	5000	150 s	250 s	3

1

VRFs are the most limiting feature. We do not recommend using more than 100 different ones on a single system.

2

Bridges are much slower to delete than other interfaces.

3

With all interfaces in the same VRF. Configuration will be slower when doing cross VRF tunnels.

4

Cross VRF interfaces are inherently limited by the number of VRFs.