Save Public Network Costs
Updated at：2025-10-16
Overview
Baidu AI Cloud advises selecting the right products and billing options based on traffic patterns to reduce public network expenses.
Requirement scenarios
Use case 1: Selecting the appropriate public network product
Public IP products differ in type and cost. Choose the product that best fits your specific use case.
Use case 2: Selecting the appropriate charge type
Based on the service traffic model, it is advisable to choose an appropriate charge type. Service traffic models generally fall into two categories: stable bandwidth and highly variable bandwidth.
Solution overview
Public network products
| Products | Application scenarios |
|---|---|
| EIP | To ensure the bandwidth capacity for a single EIP, it is recommended to purchase dedicated bandwidth for the EIP instance. Dedicated bandwidth enforces bandwidth limits only on a single EIP and remains unaffected by other services. |
| EIPGROUP | If public IP instances exhibit off-peak traffic patterns, using EIPGROUP for centralized bandwidth management simplifies operational statistics. |
| Bandwidth package | For scenarios involving prepaid EIP instances or EIPGROUP that require a temporary upgrade, it is recommended to utilize bandwidth packages. |
| Shared traffic package | For pay-as-you-go EIP instances, shared traffic packages are recommended. These packages activate immediately upon purchase, automatically offsetting traffic charges for pay-as-you-go EIP bandwidth at rates lower than standard postpay traffic fees. |
Charge type
Bandwidth remains stable
Recommended charge types:
- EIP subscription billing is ideal for scenarios with consistently stable service traffic peaks over time and for long-term use.
- EIP billed postpaid by bandwidth is appropriate for scenarios with stable service traffic peaks across time periods and for short-term use.
- EIPGROUP billed by bandwidth is suitable for scenarios where different public network instances have clear off-peak usage patterns, yet the overall bandwidth usage remains stable.
Large bandwidth fluctuations
Recommended charge types:
- EIP postpaid by traffic is appropriate for scenarios with significantly fluctuating service traffic peaks across time periods.
- Shared traffic packages are best for scenarios with anticipated service traffic volumes. These packages take effect immediately upon purchase and automatically offset traffic fees from pay-as-you-go EIP bandwidth until fully consumed or expired.
- Prepay with a bandwidth package is suitable for scenarios involving periodic traffic peaks. The prepay covers daily usage (e.g., 10:00–12:00). During peak hours, a bandwidth package can be purchased and linked to prepaid EIP instances or EIPGROUP. For example, a 100 Mbps bandwidth package used for 2 hours means paying only for those 2 hours of additional 100 Mbps peak bandwidth.
- For postpay-by-bandwidth EIPs, the bandwidth limit for instances or EIPGROUP can be adjusted anytime. By using the open API, users can automatically increase or decrease the EIP bandwidth limit based on monitored bandwidth usage, aligning with actual service traffic peaks.
- EIPGROUP billed by the enhanced 95th percentile is ideal for services prone to frequent traffic bursts. This method avoids packet loss caused by overly low bandwidth limits and prevents unnecessary costs from excessively high bandwidth peak settings.