Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Having a flash sale or a product launch? Especially if you are launching limited-time pricing or inventory, Aspenware very highly recommends, almost mandates, scaling for these scenarios. We define a flash sale as a short period of time where your resort will be driving 300% more traffic to your e-commerce site than is typical (i.e. a product launch, a pass sales price deadline, a high volume special event that sells out quickly, etc.) Please take the following steps at least 7 business days prior to the flash sale to notify and work with your Aspenware representative to ensure your site has the proper Azure tier for the sale and product configuration questions answered ahead of the sale. 

Note

IMPORTANT: If you determine that autoscaling (detailed below) is not sufficient to handle your upcoming sale, working with Aspenware to further scale your Azure resources for a temporary period will incur /wiki/spaces/DB/pages/768704654 fees. (typically between 1- 3 hrs)

Prerequisite Checklist

  1. Get your Azure environment set up for autoscale (will cover you most of the time)

  2. Determine if you need to scale your site for this event by looking at data and answering key questions.

  3. Determine the specifics of your flash sale and email Aspenware at ski-support@aspenware.com at least 7 business days in advance of any flash sale.

  4. If Queue-it is used, update safety net max user redirects following Aspenware’s confirmation of scaling.

1. Get your Azure environment set up for autoscale (will cover you most of the time)

HINT: If you aren’t already set up for auto-scaling in Azure, you should be. Talk to your Aspenware Representative about configuring this in Azure along with alerting today. However, there are some situations where even auto-scaling doesn’t cover you. This article highlights scenarios where you should be considering Azure intervention beyond auto-scaling for specific very high traffic events.

Prerequisite Checklist

  1. Determine if you need to scale your site by looking at data and answering key questions.

  2. Determine the specifics of your flash sale and email Aspenware at ski-support@aspenware.com at least 7 business days in advance of any flash sale.

  3. If Queue-it is used, update safety net max user redirects following Aspenware’s confirmation of scaling.

...

Work with your Aspenware Representative to complete the following

  • Add Auto tuning on your Azure Sql db

  • Ensure Application Insights is configured properly

  • Configure autoscaling and alerts at the level you would like around scaling events

    • We recommend a p2v2 App Service, an s3 db with autoscaling moving between 1 - 4 App Services depending on load

  • Once configured with Aspenware, set up your Queue-It safety net between40-60 max redirects (users per minute). This should cover you most of the time.

2. There will be a few outlier events where you’ll need additional Scaling. Determine if you need to scale your site for these events.

If you are unsure whether your upcoming sale will cause performance issues in the shop, check Google Analytics traffic overview filtered by the hour for data from last year's sale. Better yet, if you have Azure Application Insights data for last year, check Metrics in Application Insights filtered by the minute for data from last year's sale.

...

Note

IMPORTANT: While scaled out, Aspenware Commerce Admin changes will not take immediate effect on the store and can take between 1 hr and 24 hrs to propagate. This increases the importance of testing products end to end prior to any launch events. If in an emergency, a change with admin needs to be made and immediately take effect while your site is experiencing high traffic, you have the following options:

  • If using Queue-It - Make the change in admin, then pause the queue, which stops letting additional users in the site - wait until CPU % drops below 40% for 2-3 minutes in Azure Application Insights, then scale down to 1 instance. Once scaled-down, the change will propagate and you can scale out and restart the queue.

  • If NOT using Queue-It - Make the change in admin, close the store, wait until CPU % drops below 40% for 2-3 minutes in Azure Application insights, then scale down to 1 instance. Once scaled-down, the change will propagate and you can scale out and re-open the store.

For more details on various admin changes and how long different change types take to propagate in a scaled environment, check out this Release Guide.

...

3. Determine the specifics of your flash sale and email Aspenware Commerce

  • Answer the following questions about your upcoming flash sale:

    • When is the flash sale? (Date and time)

    • What is going on sale? (The more detail the more we can help brainstorm with you)

    • What load are you expecting? (Send data from section 1 above)

    • How long do you want to scale up your database/ how long do you expect the sale to last?

    • Identify any questions on product setup, requests for support, training, testing, etc.

    • Please indicate whether you use a Queue-it safety net.

...

Aspenware will send a calendar invite to note when we are scaling your site up with the new Azure levels indicated as well as a calendar invite to note when we are scaling your site down with the baseline Azure levels.

...

4. If Queue-It is used, update safety net max user redirects for flash sale

If you use Queue-It, please update your safety net max user redirects (throughput) to match with the level your site is set to using the table below BOTH when scaled up AND when scaled back down. 

Application Service Level

Number of (scaled) instances

DB Level

Queue it Max User Redirect (users per min)

p2v2

p2v2

1

s3

10-20

p2v2

2

s3

20-39

p2v2 (level Queue-it should be set if autoscaling configured)*

3

s4

40-59

* If set up to autoscale in Azure, you can leave Queue-it between 40-60

1-4

s4

6010-79

p2v2

5-6

s4

80-100

p2v2 or p3v2**

67+

s4+

>100

* If a store is a multi-store divide this level between the multiple stores. (i.e 30 to store A and 10 to store B)

...

HINT: