> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.quortex.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Choose the Right Balancing Strategy

Quortex Switch offers two ways to distribute traffic across your CDNs. The choice depends on your goals—whether you want to optimize for **cost**, **performance**, or **peak/off-peak flexibility**. You can select the balancing type for each segment you create.
---

# 1. Percentage-Based Balancing


![Percentage-based balancing](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/percentage-based-balancing_1busmyc.png =750x297)
This method splits traffic between selected CDNs based on predefined percentages.

###### How it works:
Each CDN is assigned a percentage. The content steering server uses these values to prioritize traffic distribution.

###### Why choose this:
Easy to adjust if issues occur.
Ideal for cost optimization:
* Use the cheapest CDN during off-peak periods.
* Add more CDNs during peak traffic for better performance.

###### Best practice:
Always configure a backup CDN with **0% traffic**. It won’t be used unless another CDN fails, ensuring service continuity.

###### Example configuration:
* CDN A: 60%
* CDN B: 40%
* CDN C (backup): 0%

![CDNs per percentages](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/percentages_nf5rye.png =750x165)

---

# 2. Capacity-Based Balancing

![Capacity-based balancing](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/capacity-based-balancing_vlj00s.png =750x329)
This method works like a **waterfall** and prioritizes CDNs based on their maximum capacity.

###### How it works:
The first CDN handles traffic until it reaches its defined capacity (in Gbps).
*  Once full, traffic flows to the next CDN, and so on.
* The last CDN acts as a backup if all others are saturated.

###### Why choose this:
Perfect for performance-driven setups.
* Ensures predictable load distribution based on CDN limits.

###### Example configuration:
* CDN A: 50 Gbps
* CDN B: 30 Gbps
* CDN C (backup): unlimited
![CDNs par capacity](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/capacity_21fce1.png =750x158)
---

**Tip:** You can mix strategies across segments to adapt to traffic patterns and business priorities.
---


