Cloud 9.04
Upsize Environment
Understanding capacity scaling, 72-hour advance notice, 5-day duration, and contracted days calculation.
Exam Critical: Understanding upsizing requirements, advance notice, duration, and contracted days calculation is important for the exam!
Upsize Environment
mindmap
root((Upsizing))
Capacity Range
12 CPUs 48GB RAM
Up to 120 CPUs 480GB RAM
Pro only
Advance Notice
72 hours required
Example Monday surge
Submit Wednesday
Duration
5 days at a time
Automatic if needed
Contracted days
History URL
View upsizing history
Project specific
Track usage
Contracted Days
ECE12 to ECE24 45 days
ECE12 to ECE48 22 days
Can be mixed
Upsizing Overview
What is Upsizing?
Capacity Scaling
Upsizing temporarily increases your environment's resources (CPU and RAM) to handle traffic spikes or special events.
Available For:
- Pro environments only
- Starter plans do not support upsizing
- Production and staging environments
Capacity Range
How Much Can You Upsize?
Pro Environment Scaling
Pro environments can upsize from 12 CPUs/48GB RAM to 120 CPUs and 480GB RAM.
| Plan | CPUs | RAM | Description |
|---|---|---|---|
| ECE12 (Base) | 12 | 48 GB | Standard Pro production |
| ECE24 | 24 | 96 GB | 1 level upsize |
| ECE48 | 48 | 192 GB | 2 levels upsize |
| ECE96 | 96 | 384 GB | 3 levels upsize |
| ECE120 (Max) | 120 | 480 GB | Maximum capacity |
Advance Notice Requirement
72-Hour Rule
Critical Requirement
To increase the capacity, you must submit a ticket 72 hours in advance (if you expect a surge of traffic on Monday, you should submit the ticket on at least the Wednesday before).
Planning Timeline
| Event Date | Minimum Ticket Submission | Hours Before |
|---|---|---|
| Monday | Wednesday (previous week) | 72+ hours |
| Friday | Tuesday (same week) | 72+ hours |
| Sunday | Thursday (previous week) | 72+ hours |
Example Scenario:
- Event: Black Friday sale on Friday, November 24
- Traffic surge expected: 10x normal traffic
- Action: Submit upsize ticket by Tuesday, November 21
- Upsize level: ECE48 or ECE96 (depending on estimates)
Upsize Duration
Five-Day Periods
Fixed Duration
Magento will upsize the server for five days at a time.
How It Works:
- Minimum upsize duration: 5 days
- Cannot request shorter periods
- Can extend by requesting additional 5-day periods
- Charged in 5-day increments against contracted days
Example Timeline
Submit Ticket: Monday, Nov 20 (for Friday, Nov 24 event)
Upsize Start: Friday, Nov 24, 12:00 AM
Upsize End: Tuesday, Nov 28, 11:59 PM
Total Duration: 5 daysAutomatic Upsizing
Emergency Site Availability
Automatic Protection
Support will also upsize automatically if it is necessary to keep the site available (this will still affect contracted upsizing days).
When Automatic Upsizing Occurs
Triggers:
- Site becomes unresponsive due to resource exhaustion
- High CPU usage causing timeouts
- Memory exhaustion crashes
- Unexpected traffic spikes
Important Note:
Even though automatic upsizing is for emergency availability, it still counts against your contracted upsizing days. Plan ahead to avoid using contracted days unnecessarily!
Viewing Upsize History
Track Your Usage
History URL
You can also view the upsizing history with the following URL:
https://cloud.magento.com/project/{PROJECT_ID}/services/clusterresize
Example
# Replace {PROJECT_ID} with your actual project ID
https://cloud.magento.com/project/abc123xyz/services/clusterresizeWhat You Can See:
- Past upsize events
- Duration of each upsize
- Level of upsize (ECE24, ECE48, etc.)
- Contracted days used
- Remaining contracted days
- Automatic vs. requested upsizes
Contracted Days Calculation
Understanding Day Allocation
Larger Upsize = More Days Used
The larger the upsize, the more contracted days are used.
Example: ECE12 Base Plan
| Upsize To | Levels Up | Days Available (per year) | 5-Day Periods Available |
|---|---|---|---|
| ECE24 | 1 level up | 45 days | 9 periods (45 ÷ 5) |
| ECE48 | 2 levels up | 22 days | 4.4 periods (22 ÷ 5) |
| ECE96 | 3 levels up | ~11 days | ~2 periods |
Key Examples from Documentation:
- If the merchant is on an ECE12 plan, and they need to migrate to an ECE24, then you have 45 upsize days available (45 days available for the next level up).
- If you need to upsize to an ECE48 (2 levels up), then 22 days are available.
Mixing Upsize Levels
Flexible Usage
Can Be Mixed
Note that these can be mixed.
Example Scenario
Annual Event Calendar:
- Black Friday (November): ECE48 for 5 days = Uses 5 days of ECE48 allocation (22 total)
- Cyber Monday (November): Already covered by Black Friday upsize
- Holiday Season (December): ECE24 for 10 days = Uses 10 days of ECE24 allocation (45 total)
- Valentine's Day (February): ECE24 for 5 days = Uses 5 more days of ECE24 allocation
- Mother's Day (May): ECE48 for 5 days = Uses 5 more days of ECE48 allocation
Total Usage:
- ECE24: 15 days used out of 45 available (30 days remaining)
- ECE48: 10 days used out of 22 available (12 days remaining)
Requesting an Upsize
How to Submit Request
Step 1: Prepare Information
- Event date and time
- Expected traffic increase (estimate)
- Desired upsize level (ECE24, ECE48, etc.)
- Duration needed (5-day minimum)
Step 2: Submit Support Ticket
Ticket Details:
- Log in to Magento Cloud Console
- Navigate to Support
- Create new ticket
- Subject: "Upsize Request for [Event Name]"
- Include:
- Event date and start time
- Requested upsize level
- Expected traffic volume
- Business justification
- Submit at least 72 hours before event
Step 3: Confirmation
- Support team reviews request
- Confirms availability of contracted days
- Schedules upsize
- Sends confirmation with details
Best Practices
Upsizing Guidelines
Do's
- Plan ahead: Submit 72+ hours in advance
- Estimate traffic: Use analytics to predict needs
- Right-size upsize: Don't over or under-estimate
- Track contracted days: Monitor usage throughout year
- Mix levels wisely: Use appropriate level for each event
- Test before event: Verify site handles traffic
- Monitor during event: Watch performance metrics
- Review history: Check past usage patterns
Don'ts
- Don't wait until last minute: 72-hour minimum required
- Don't waste contracted days: Plan carefully
- Don't ignore automatic upsizes: They count against allocation
- Don't over-upsize: Use smallest level that meets needs
- Don't forget to check history: Track remaining days
Common Scenarios
When to Upsize
Scenario 1: Seasonal Sale Event
Event:
Black Friday / Cyber Monday weekend sale
Timeline:
- Event dates: Friday, Nov 24 - Monday, Nov 27
- Expected traffic: 15x normal
- Action: Request ECE48 upsize
- Submit by: Tuesday, Nov 21 (72+ hours before)
- Duration: 5 days (covers entire weekend + buffer)
- Days used: 5 out of 22 ECE48 days
Scenario 2: Product Launch
Event:
New product launch with heavy marketing
Timeline:
- Launch date: Wednesday, March 15
- Expected traffic: 8x normal
- Action: Request ECE24 upsize
- Submit by: Sunday, March 12 (72+ hours before)
- Duration: 5 days
- Days used: 5 out of 45 ECE24 days
Monitoring During Upsize
Performance Tracking
Key Metrics to Watch
- CPU usage: Should stay below 80%
- Memory usage: Monitor for exhaustion
- Response times: Track page load speeds
- Error rates: Watch for 503/502 errors
- Queue depth: Monitor Fastly/Redis queues
Tools
- New Relic APM
- Fastly dashboard
- Magento Cloud monitoring
- Custom dashboards
Exam Tips
Key Points to Remember
- Capacity range: 12 CPUs/48GB RAM to 120 CPUs/480GB RAM
- Pro only: Upsizing available for Pro environments only
- Advance notice: Submit ticket 72 hours in advance
- Example: Monday event = submit Wednesday before
- Duration: Magento upsizes for 5 days at a time
- Automatic upsizing: Support will upsize if necessary (still counts against days)
- History URL: https://cloud.magento.com/project/{PROJECT_ID}/services/clusterresize
- Larger upsize = more days: More capacity uses more contracted days
- ECE12 to ECE24: 45 upsize days available (1 level up)
- ECE12 to ECE48: 22 upsize days available (2 levels up)
- Can be mixed: Use different levels throughout year
- Minimum duration: 5 days per upsize period
