What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
No single cloud subscription guarantees a smooth Black Friday. Adobe Commerce on cloud infrastructure offers capacity options for eligible customers, including autoscaling and temporary cluster upsizes, but Adobe’s own guidance still calls for advance planning, support coordination, load testing, recovery testing, and monitoring. Whether you need that platform depends on your workload, architecture, and operations—not the holiday name alone.
What the title gets right—and what it doesn’t
You do not need to buy Adobe Commerce Cloud as a substitute for preparing your store. But that does not mean every retailer can safely handle peak traffic without cloud infrastructure, or that an existing setup will be adequate. The available Adobe guidance explains how certain Commerce on cloud infrastructure capabilities work; it does not compare platforms or establish a universal minimum setup for Black Friday.
As an Amazon Associate I earn from qualifying purchases.
The useful question is: can your specific storefront, checkout, integrations, and underlying services handle the traffic you expect, and can your team detect and recover from problems? Adobe’s scalability guidance treats known peaks as something to plan for, even when autoscaling is available.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhat Adobe Commerce on cloud infrastructure can do
Adobe documents horizontal autoscaling for web nodes in scaled architecture projects and vertical autoscaling for standard Pro and scaled architecture. These are not unlimited, automatic capacity guarantees: eligibility and contracted resource limits matter, and Adobe Support is involved in enabling autoscaling.
#1 Best Overall
Horizontal scaling adds web nodes
According to Adobe’s autoscaling documentation, web nodes are added when CPU across active web nodes reaches 75% for one minute and traffic has increased by 20% for five consecutive minutes. Nodes are removed when CPU is at 60% for 20 minutes. Adobe sets minimum and maximum thresholds according to contracted resource limits. These mechanics apply to scaled architecture projects, not every deployment.
Vertical scaling resizes existing nodes
Vertical autoscaling resizes nodes in response to memory pressure. Adobe sets the thresholds; customers cannot currently configure them. Adobe says resizing typically takes 20–30 minutes, during which the node is temporarily removed from the load balancer. That delay matters if a system is already under pressure.
Adobe says autoscaling is intended to capture unanticipated events, but recommends submitting a support request for an expected event as well. It is enabled through Adobe Support, initially in staging; customers complete load testing before Adobe enables it in production. Read the details in Adobe’s autoscaling documentation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check whether your architecture is eligible
Adobe’s scaled architecture separates web servers from database and service nodes. The web tier can add nodes horizontally, while the service tier scales vertically; database scaling has its own constraints. As a result, adding web capacity may not resolve a bottleneck in the database, search, cache, queues, or an external service.
Adobe says scaled architecture is available to Pro 48 cluster or greater accounts. Its autoscaling options also differ by architecture: horizontal web-node autoscaling is for scaled architecture, while vertical autoscaling is available for standard Pro and scaled architecture. Confirm your actual project type, cluster, contracted limits, and eligibility with Adobe rather than assuming a feature applies to your account. See Adobe’s Scaled Architecture documentation.
Plan capacity for a known peak
For customers requesting a temporary cluster upsize, Adobe’s holiday guidance, last updated September 30, 2026, says to submit a support ticket at least 48 business hours in advance. It also advises requesting capacity as early as possible for the holiday season because capacity around Black Friday and Cyber Monday is limited. Include the date range and desired cluster size, and coordinate with your account manager. The lead time is a minimum, not a reason to wait until the last two business days.
A temporary upsize allocates additional computing resources, but it should be based on an expected workload and confirmed with Adobe for your account. The guidance does not publish generally applicable prices or guarantee that a particular request will be available. Details are in Adobe’s scalability and capacity planning guide.
Prepare the whole request path, not just the web tier
A busy storefront can be limited by a component other than its web servers. Map the path from a shopper’s page request through cache, application, database, search, queues, payment, and other integrations. Identify where capacity is constrained and who owns each dependency.
Adobe’s reference architecture recommends Varnish for full-page caching and discusses cache sizing, web-node redundancy, database and queue performance, and search capacity. That guidance describes physical-server deployments, not an exact configuration recipe for Commerce on cloud infrastructure. Treat it as a set of topics to evaluate, then verify the appropriate settings for your own cloud architecture. See Adobe’s reference architecture.
Rank #4
Adobe also describes Fastly edge locations checking cache first; on a cache miss, the request checks the selected shield point of presence before proceeding to origin. Origin shielding is not enabled by default. Adobe recommends selecting a shield close to the Commerce origin data center. Verify whether it is enabled and correctly selected for your environment in the holiday readiness guidance.
Test before the campaign
Adobe recommends load and recovery tests before major campaigns to validate scaling configurations and rollback plans. A useful test should represent your expected traffic and the operations that matter: browsing, search, cart, checkout, and the integrations your store relies on. Testing only a cached landing page may not expose a checkout or database bottleneck.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Use a representative workload and confirm which part of the request path is under pressure.
- Validate autoscaling or other capacity changes in staging before relying on them in production.
- Exercise recovery and rollback procedures, not only the successful peak-load case.
- Agree in advance who can request capacity changes and how incidents will be escalated.
These are planning steps, not a guarantee that a test can reproduce every live condition. Make sure the team can observe the system during the event: Adobe’s cloud documentation points to New Relic for CPU, RAM, host count, and instance changes. Monitor application behavior and dependencies too; a host-count graph alone cannot establish that checkout is healthy.
Best Value
How to decide whether you need a different platform or more capacity
Use evidence about your own business rather than treating “cloud” as a Black Friday checklist item. Before committing to a platform change or a capacity request, establish:
- Expected demand: your likely traffic and transaction workload, informed by your own past peaks and campaign plans.
- Current bottleneck: whether the limiting component is the web tier, database, cache, search, queue, payment path, or another dependency.
- Architecture and eligibility: which Commerce deployment and cluster you have, and which capacity mechanisms your account supports.
- Validation: whether realistic load and recovery tests have been completed and rollback steps are understood.
- Operational visibility: whether staff can see resource changes, response behavior, and dependency health during the event.
- Capacity terms: your contracted limits, account-specific upsize availability, and any associated commercial terms.
The reviewed guidance concerns Adobe Commerce on cloud infrastructure. Do not assume its autoscaling or capacity details apply unchanged to self-managed Adobe Commerce or Adobe Commerce as a Cloud Service.
What Adobe’s performance figures do—and don’t—tell you
Adobe’s March 2023 vendor article reports benchmark results for Adobe Commerce on Cloud version 2.4.5. Adobe described the criteria as intended to mimic an enterprise B2C organization. The reported figures are:
| Reported measure | Adobe’s published figure |
|---|---|
| Orders per hour | 208,000 |
| Pageviews per hour | 2 million |
| Effective SKUs | 242 million |
| GraphQL calls per minute | 10,500 |
| Concurrent back-office users | 500 |
These are Adobe-published results for its stated version and test context, not an independent Black Friday result, a forecast for your implementation, or an uptime promise. Adobe’s article also describes infrastructure and application SLA figures for Adobe Commerce on Managed Services; those are vendor-published service claims from 2023, not a guarantee of successful peak performance for an individual store. See Adobe’s benchmark article.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
