Versions Compared

Key

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

...

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 10% 40% for 2-3 minutes in Azure Application insightsInsights, 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 10% 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.

...

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.

3. If Queue-

...

It is used, update safety net max user redirects

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

1

s3

10-50

p2v2

2

s4s3

20

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

3

s4

40

p2v2

64

s7s4

80

p2v2

106

s7s4

100

p2v2 or p3v2**

6+

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)

**If you’d like to scale beyond 100 users per minute, please contact Aspenware.

If using Aspenware Identity Authentication for Commerce

Application Service Level

Number of (scaled) instances

DB Level

Queue it Max User Redirect (users per min)

p2v2

1

s3

15

p2v2

2

s4

40

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

3

s4

60

p2v2

6

s7

100

p2v2

10

s7

120

...