Set up and optimize delivery
You need a delivery configuration ("property") set up to manage delivery of your content via the Akamai edge network.
Optimize your property
Based on your Akamai delivery product, set up your property to optimize it.
-
Adaptive Media Delivery (AMD). Have a look at your property settings to view your behaviors. The default rule in an AMD property is pre-populated with several behaviors you can use to optimize delivery. Set it up to deliver live streaming video (low-latency), on-demand streaming (redundant), or both. Also, see AMD Content Characteristics recommendations, below.
-
Download Delivery. Review the rules and behaviors you have set for your Download Delivery property. Of note is the Content Characteristics behavior. Use it define specifics for your content to help optimize its delivery through Cloud Wrapper.
-
Dynamic Site Acceleration (Limited Availability support for Cloud Wrapper). A new Dynamic Site Acceleration property is predefined with some recommended rules and behaviors. Ensure that HTTP/3, mPulse, and some sort of Caching are enabled. See the Property Manager user documentation for more information.
-
Ion (Limited Availability support for Cloud Wrapper). A new Ion property is predefined with several recommended rules and behaviors. Ensure that HTTP/3, mPulse, Adaptive Acceleration, and some form of Caching are enabled. See the Ion user documentation for more information.
-
Object Delivery. Review the rules and behaviors you have set for your Object Delivery property. Of note is the Content Characteristics behavior. Use it define specifics for your content to help optimize its delivery through Cloud Wrapper.
Properties need to be in production
- Properties need to be in production. All properties need to be actively delivering content on Akamai's production network to be included in a Cloud Wrapper configuration. See Determine your requirements for specifics.
- Web delivery is Limited Availability. Support forCloud Wrapperwith our Dynamic Acceleration and Ion products is in Limited Availability. Talk to your account team about access to it.
Content needs to be cacheable
Cloud Wrapper's fundamental support is based on housing your cacheable content in your footprint, to help reduce load on your origin server. If you're specifically distributing non-cacheable content (no-store or bypass cache), you can't add Cloud Wrapper to your property.
Unsupported behaviors
These features aren't supported for use with Cloud Wrapper. You'll need to remove or disable them from your property:
Tiered Distribution with AMD, Download Delivery, and Object Delivery
With these three products, Tiered Distribution is automatically enabled and optimized in the background of the Origin Characteristics behavior in the Default Rule. You don't need to add the standalone version of the Tiered Distribution behavior to your property. Rely on the settings that are automatically applied via Origin Characteristics.
AMD Content Characteristics recommendations
Use these settings to get better performance with Cloud Wrapper when streaming on-demand video via an AMD property:
- Catalog size. Set this to Large or Extra Large.
- Popularity Distribution. Set this to Long Tail.
- Enable <media format>. Click Yes for each media format you want to enable for streaming.
- Segment Duration. Each media format has a default segment size which is pre-defined. Unless you know your segments are a different size, leave this at the default.
- Origin Object Size. If your origin objects are over 10 MB you should set this to 10-100 MB or Greater than 100MB.
You may want partial object caching
Partial object caching doesn't directly impact disk usage, but it can increase offload at edge, which will create less demand from Cloud Wrapper.
We recommend that you verify the size of your delivery objects on your origin, and select the appropriate size to ensure that partial object caching is enabled or disabled, as necessary.
Updated about 2 months ago