Tencent Cloud EdgeOne
- Release Notes and Announcements
- Security Announcement
- Announcements
- Product Introduction
- Purchase Guide
- Billing Items
- Basic Service Fees
- Value-added Service Fees
- Instructions for overdue and refunds
- Getting Started
- Domain Service&Origin Configuration
- Domain Service
- Hosting DNS Records
- Domain Connection
- Traffic Scheduling
- HTTPS Certificate
- HTTPS Configuration
- SSL/TLS Security Configuration
- Origin Configuration
- Load Balancing
- Related References
- Origin-pull configuration
- Related References
- Site Acceleration
- Access Control
- Cache Configuration
- EdgeOne Cache Rules
- Cache Configuration
- Clear and Preheat Cach
- File Optimization
- Network Optimization
- HTTP/3(QUIC)
- QUIC SDK
- Modifying Header
- Modify the response content
- Rule Engine
- Related References
- Request and Response Actions
- DDoS & Web Protection
- DDoS Protection
- Configuration of Exclusive DDoS protection Rules
- Related References
- Web Protection
- Rate Limiting
- Bot Management
- Related References
- Related References
- Image&Video Processing
- Edge Functions
- Runtime APIs
- Streams
- Images
- Sample Functions
- Best Practices
- L4 Proxy
- Obtaining Real Client IPs
- Obtaining Real Client IPs Through Protocol V1/V2
- Data Analysis&Log Service
- Log Service
- Real-time Logs
- Data Analysis
- Related References
- Legacy Console Relevant Documentation
- Security Analysis
- Alarm Service
- Version Management
- Site and Billing Management
- Site Management
- General Policy
- Terraform
- Practical Tutorial
- Automatic Warm-up/Cache Purge
- Resource Abuse/hotlinking Protection Practical
- HTTPS Related Practices
- Acceleration Optimization
- Scheduling Traffic
- Origin-pull Based On User IP/geolocation
- APK Dynamic Packaging
- Data Analysis and Alerting
- API Documentation
- Making API Requests
- Site APIs
- Acceleration Domain Management APIs
- Site Acceleration Configuration APIs
- Edge Function APIs
- Alias Domain APIs
- Security Configuration APIs
- Layer 4 Application Proxy APIs
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- DNS Record APIs
- Content Identifier APIs
- Old Version APIs
- Version Management APIs
- Common Guidelines
- FAQs
- Troubleshooting
- Tool Guide
- Speed Test Tools
- Diagnostic Tool
- Agreements
Audio and Video Pre-pulling
Last updated: 2024-10-25 18:06:58
Overview
When the network connection is unstable or the audio and video files are too large, users may encounter problems such as first-frame loading delay or playback lag. The audio and video pre-pulling feature of EdgeOne can effectively improve these problems. It automatically caches part of the audio and video data before the user clicks and plays, significantly shortening buffering time and ensuring a smooth viewing experience even under unstable network connection. Additionally, audio and video pre-pulling is the default configuration policy of EdgeOne, with optimal parameters set for audio and video scenarios. Users only need to select the corresponding recommended scenario when adding a domain name to enable the feature by default.
Feature Principle
HLS/DASH files: When the client requests an m3u8/mpd file, the edge node of EdgeOne pulls ts/m4s segments in advance to increase the speed of response to subsequent requests.
MP4/FLV files: When the client initiates a range request, by expanding the scope of the range request before the origin-pull, files are pre-cached to the edge node of EdgeOne to improve response efficiency.
Directions
If you need to enable the audio and video pre-pulling feature, you can refer to the following steps:
Note:
The current guidance on directions is only applicable to the scenario of newly created domain names. If you need to enable the audio and video pre-pulling feature for domain names already added under your account, contact your business personnel for assistance.
1. Log in to the EdgeOne console, click Site List in the left menu bar, and click the site to be configured on the site list.
2. On the site details page, click Domain Name Service, select Add domain name, and refer to the description of domain name configuration items to complete the basic configuration of the domain name. Click the Next button.
3. In the Recommended configuration (Optional) step, click to select the audio and video on demand card, and choose to use the recommended configuration for this scenario. When audio and video files are added under this domain name, the audio and video pre-pulling operation will be triggered by default.
4. Click Next and complete other subsequent domain name configuration operations.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No