Getting Started with Performance

1. Create a property. If you have already performed this step, proceed to the next step.
   Learn more.
2. Create rules that define how Edgio handles your traffic.
   If you prefer code to UI, then try our CDN-as-code approach to configuration instead.
3. Deploy your updated property to Edgio.
4. Serve production traffic over Edgio by updating your site’s DNS to point to our service.

Creating Rules #

Rule #1: Default Caching Policy #

1. Load the Rules page.
   1. From the Edgio Console, select the desired private space or organization.
   2. Select the desired property.
   3. From the left-hand pane, select the desired environment from under the Environments section.
   4. From the left-hand pane, select Rules.

   

2. Add a rule by clicking + Add Rule.
   You may add conditions and features to a rule. A condition identifies a set of requests and a feature defines the action that will be applied to them.

   We will not add a condition to this rule. A rule without a condition applies to all requests.
3. Define a default policy for how long your clients (e.g., web browsers) will cache your content.
   1. Click + Add Feature.
   2. Select Set Client Max Age.
      Typing automatically filters this list. If you can’t remember the name of the feature, type a keyword (e.g., Age) to filter the list for relevant results.
   3. Set the duration to 5 minutes.

      

   4. Click Add Feature.
      Your rule should now look similar to this:

      

4. Define a default policy for how long our CDN will cache your content for 200 OK responses.
   1. Click + Add Feature.
   2. Select Set Max Age.
      You may notice that Set Client Max Age is no longer available for selection. This is due to the fact that you may only add a feature a single time per rule.
   3. Set the duration to 1 day for 200 OK responses.

      

   4. Click Add Feature.
      Your rule should now look similar to this:

      

Rule #2: Path-Specific Caching Policy #

1. Add a rule by clicking + Add Rule.
2. Define the type of requests to which this rule will be applied.
   1. Click +Add Condition.
   2. Select Path.
   3. Leave the Operator option to matches (simple).
   4. Match for requests whose relative path starts with /news/ by setting the Match Value option to: /news/:path*
      The matches (simple) operator supports named parameters. A named parameter (e.g., :path) represents a URL segment. Appending a * matches everything that follows that URL segment.
      Your condition should now look like this:

      

   5. Click Add Condition.
3. Define how long our CDN will cache content for 200 OK responses to the requests identified in the previous step.
   1. Click + Add Feature.
   2. Select Set Max Age.
   3. Set the duration to 1 minute for 200 OK responses.
   4. Click Add Feature.
      Your rule should now look similar to this:

      

Deploying Your Property #

1. Click Deploy Changes from any page within the production environment.

   

2. When prompted, provide a brief description for this change and then click Deploy Changes.
   Example: Setting a default caching policy and a caching policy for /news/ requests.
3. From the left-hand pane, select Deployments.
4. View the deployment by clicking on the version number (e.g., #2) for the latest deployment.

   

5. Preview your site by clicking the second edge link displayed under the URL section.

   

• Assess performance and caching behavior through Edge Insights and Core Web Vitals.
• Fine-tune your configuration by adding rules and then redeploying your property.
• Once you are ready to serve production traffic through Edgio, update your site’s DNS to point to our service.
  Learn more.