Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page
Help Center/ Content Delivery Network/ Troubleshooting/ Why Is It Still Slow to Access a Domain Name That Has Been Added for CDN Acceleration?

Why Is It Still Slow to Access a Domain Name That Has Been Added for CDN Acceleration?

Updated on 2024-06-06 GMT+08:00

Symptom

After CDN acceleration is enabled, access to a web page or app resources is still slow.

Check Items

  • Whether CDN acceleration is enabled for the domain name
  • Whether the CDN cache is hit
  • Whether inter-carrier or cross-province access is involved
  • Whether cache rules are appropriate
  • Whether the content is prefetched
  • Whether the client network is faulty

Procedure

  1. Check whether CDN acceleration is enabled for the domain name.
    NOTE:

    If you have just added an acceleration domain name on the CDN console and are testing the domain name before adding a CNAME record, skip this step and configure the domain name as instructed in Getting Started.

    Check whether the domain name is resolved to CDN. Take the Windows OS as an example. Open the Command Prompt and run the following command:

    nslookup -qt=cname Acceleration domain name

    If the command output contains .c.cdnhwc1.com, the CNAME record has taken effect.

    • If the command output does not contain .c.cdnhwc1.com, CDN acceleration has not taken effect for the added domain name. The CNAME record has not been added to your domain's DNS records. Contact your DNS service provider to configure the CNAME record as instructed in Configuring a CNAME Record.
    • If the CNAME record was correctly configured, check the TTL of the previous resolution record of the domain name on the same resolution line. The TTL specifies the cache duration of a resolution record on the local DNS server. The newly added CDN CNAME record takes effect only after the TTL of the previous record expires.
  2. Check whether the CDN cache is hit.
    On the Google Chrome browser, press F12 and click the Network tab. View the response headers of the URL of a specific resource and perform the following operations:
    • Check the value of the x-hcs-proxy-type header. The value 1 indicates that the cache is hit, and the value 0 indicates that the cache is not hit.
    • If the x-hcs-proxy-type header does not exist, check the value of the X-Cache-Lookup header. Value Hit From MemCache, Hit From Disktank, or Hit From Upstream indicates that the cache is hit, whereas other values indicate that the cache is not hit.
    • If neither the x-hcs-proxy-type nor X-Cache-Lookup header exists, check the value of the age header. Values greater than 0 indicate that the cache is hit, and the value 0 indicates that the cache is not hit.

    If no cache is hit, go to 4 to check the cache rule settings.

    If the cache is hit, proceed to the next step.

  3. Check whether inter-carrier or cross-province access is involved.

    Perform the following steps:

    1. Obtain the client IP address and local DNS.
    2. Check the client IP address and local DNS to see whether a proxy is used. If a proxy is used, inter-carrier and cross-province access may occur, affecting the access speed.

      Example 1: A user in the Hebei province uses the Broadcasting Network to access the acceleration domain name. The client IP address is assigned by Beijing Unicom but the local DNS is assigned by Shijiazhuang Telecom. The access speed is greatly affected by inter-carrier access.

      Example 2: A user in Beijing uses the Broadcasting Network to access the acceleration domain name. The client IP address is assigned by Beijing Unicom but the local DNS is assigned by Guangdong Telecom, so the CDN scheduling system assigns the nearest PoP in Guangdong to return resources based on the local DNS. As a result, the access is slow.

    3. Currently, Huawei Cloud CDN supports China Telecom, China Unicom, China Mobile, China Tietong, CERNET, and Dr. Peng.
  4. Check cache rules.
    • Check whether the configured TTL is 0 or a small value. If CDN does not cache content or the TTL is too short, CDN frequently pulls content from the origin server, and the origin pull cannot be accelerated.
    • Check the cache settings on the origin server. If no-cache, private, or no-store is set on the origin server and Origin Cache Control is enabled on the CDN console (this function is disabled by default), CDN cannot cache content. CDN needs to pull content from the origin server, and the origin pull cannot be accelerated.
    • Check the priority of cache rules. The greater the value, the higher the priority.
    • Check whether URL parameters are retained. If URL parameters are retained, when users request a file using URLs containing different parameters, CDN considers that each request is new, and pulls the file from the origin server for each request. For details, see Cache Rules.
    • For more cache settings, see Setting the Cache TTL.
  5. Check whether the content is prefetched.

    If the content has not been prefetched and is requested for the first time, CDN PoPs will pull it from the origin server. In this case, slow access to the content is normal.

    NOTE:

    When enabling CDN for the first time, you can prefetch large files or videos.

  6. Check the client network.

    Ping the domain name to which access is still slow after CDN acceleration to check the network delay and packet loss. If the network delay is long or severe packet loss occurs, check the network connection of the client.

If the fault persists even after taking the previous steps, submit a service ticket.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback