Loading

Performance Impact with Salesforce Maintenance — Understanding Cache Warm-Up

Fecha de publicación: May 4, 2026
Descripción

There are chances of slow transactions due to the cache not being warmed up sufficiently post maintenance. After any maintenance activity where the database is restarted or a Site Switch occurs, it takes time to warm the cache. No ETA can be provided for cache warm-up as it is managed by algorithms and the volume of traffic the org generates. 

 

What Is Cache? — Cold Cache vs. Warm Cache

A cold cache is the state immediately after a restart or failover, where no data is stored in memory. Every request must be served from Database storage disk — the slowest possible path which is orders of magnitude slower than reading from RAM.
 
What Is Cache Warm-Up?
Salesforce infrastructure — like all enterprise database and application platforms — relies on in-memory caching to serve data quickly. Caching works by storing frequently accessed data in fast RAM memory rather than reading it from slower disk storage every time. This is what makes your everyday Salesforce experience fast and responsive.
When a database is restarted or your org is moved to a new instance, this in-memory cache starts completely empty — a state known as cold cache. As real user traffic hits the system, the cache gradually fills with frequently accessed data — a state known as warm cache — and performance returns to normal baseline.
 
Real-Life Scenario:
Your Salesforce org undergoes a scheduled Instance Refresh overnight — moving from NA45 to NA135. The next morning, your sales team logs in and notices that loading the Accounts list view takes 6–8 seconds instead of the usual 1–2 seconds. Reports that normally run in 30 seconds are taking 3–4 minutes. It is the expected cold cache behavior. The Database on NA135 has no data in its buffer pool yet. As users continue working normally throughout the morning, the cache fills up and by mid-morning performance is back to baseline.

How Long Does Warm-Up Take?

Warm-up time varies depending on the size of your org and the volume of user activity. For most orgs, performance returns to normal within a few hours of regular use. No action is required on your part.

 

Solución
What Customers Can Do
  • Continue normal use — organic user traffic is the only way to warm the cache; the more users who log in and work normally, the faster performance returns to baseline
  • Run your most common workflows first — open frequently used list views, run your most common reports, load your highest-traffic objects (Accounts, Cases, Opportunities) — this directly exercises the DB buffer pool and accelerates warm-up
  • Check Salesforce Trust Status to confirm maintenance has fully completed before attributing slowness to other cause
  • Avoid running large bulk data exports or full-table SOQL queries immediately post-maintenance — these can perform full table scans from Database cluster that load rarely-accessed data blocks into the buffer pool, evicting frequently-accessed blocks and slowing warm-up for interactive users
Número del artículo de conocimiento

000395540

 
Cargando
Salesforce Help | Article