Skip to main content
Version: 1.2.x

TSB Resource Consumption and Capacity Planning

The purpose of this document is to outline the general guidelines for capacity planning of Tetrate Service Bridge in Management and Control planes.

These parameters apply to production installations. TSB may and will run with minimal resources in demo-like environments.


The resource provisioning guidelines described in this document are very conservative. The resource provisioning described in this document refers to the vertical resource scaling, multiple replicas of the same TSB components do not share the load and should be used for high availability purposes only.

Resource requirements with 1 cluster registered and 1 service deployed in the cluster.

ComponentvCPU #Memory MiB
TSB server (Management Plane) 12512
XCP Central Components 22128
XCP Edge1128
Front Envoy150
TSB UI1256
1 Including the Kubernetes operator and persistent data reconciliation processes.
2 Including the Kubernetes operator.

The TSB stack is mostly CPU-bound. Additional clusters registered with TSB via XCP increase CPU utilisation by ~4%.

The effect of additional registered clusters or additional deployed workload services on memory utilisation is almost negligible. Likewise, the effect of additional clusters or workloads on resource consumption of the majority of TSB components is mostly negligible, with the notable exceptions of TSB, XCP Central component, TSB UI and IAM.


Components that are part of the visibility stack (e.g. OTel/Zipkin, etc.) have their resource utilisation driven by requests, thus the resource scaling should follow the user request rate statistics. As a general rule of thumb, more than 1 vCPU is preferred. It is also important to notice that the visibility stack performance is largely bound by Elasticsearch performance.

Thus, we recommend vertically scaling the components by 1 vCPU for a number of deployed workflows:

Management Plane

ComponentScaling factor
TSB server25-50 clusters, 150-200 services
TSB UI50-100 services
XCP Central25-50 clusters, ~500 services
OAP50-100 services
Zipkin50-100 services
IAM~500 services
Front Envoy~1000 services