CDN Pro 비용 & 커버리지

We organized our global Points of Presence (PoPs) into 4 server groups based on cost. From lowest to highest, the groups are: Standard, Premium, Deluxe, Ultra.  Depending on your needs, you can choose the server groups to use for your visitors according to country and ISP. This lets you maximize performance and minimize costs. 

For consistency, server hardware is largely the same across server groups. The main difference between different server groups is the bandwidth cost charged by our vendors (ISPs). A PoP in the “ultra” group is more expensive than one in the “standard” group, but does not necessarily deliver better performance than a “standard” PoP. Performance experienced by each end user is determined by the connectivity between the user and the PoP. Adding the “ultra” group to serve a region just provides our GSLB algorithm more PoPs to choose from, such that the end users in that region are more likely to get a PoP with better connectivity.

No. The CDN Pro GSLB assigns PoPs primarily based on performance. Adding “ultra” to serve a region enables the GSLB to choose from a larger pool of PoPs for that region. If the algorithm determines that a request will be better served by a “standard” PoP, the traffic is still served from that PoP and incurs a “standard” charge.

In general, the “Standard” group delivers excellent coverage for North America , Europe, and some regions in Asia. Adding the “Premium” group can enhance the performance in those areas as well as the Middle East. Adding “Deluxe” delivers good performance in APAC countries. Adding “Ultra” gives you our best possible performance in all areas including South America, Oceania and Africa.  We invite you to try different configurations to determine the right balance between performance and cost.

CDN Pro does not charge for TLS certificates and HTTPS accesses.  You can BYO certificate for your property domain configuration.  CDN Pro also supports self-signed certificates and Let’s Encrypt generated certificates.

CDN Pro collects CPU usage based on NGINX’s “event-driven, non-blocking” architecture. Every request to CDN Pro is put to sleep when waiting for I/O activities, awakened when some data is ready to be processed, and then put to sleep again when the processing is completed. This can occur many times during the lifecycle of a request. CDN Pro uses the function clock_gettime() on Linux to obtain the amount of CPU time, in nanoseconds, spent on each active interval of each request and accumulated along the way. At the end of the request’s lifecycle, we collect the total consumed CPU time for the request, just like how we treat the bytes transferred.