Force.com Apex Code Developer's Guide

Getting Started
Writing Apex
Ways to Invoke Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Approval Processing
Chatter Answers and Ideas
Chatter in Apex
Moderate Chatter Private Messages with Triggers
Communities
Email
Platform Cache
Platform Cache Features
Platform Cache Considerations
Platform Cache Limits
Platform Cache Partitions
Store and Retrieve Values from the Session Cache
Use a Visualforce Global Variable for the Session Cache
Store and Retrieve Values from the Org Cache
Salesforce Knowledge
Lightning Connect
Salesforce Reports and Dashboards API via Apex
Force.com Sites
Support Classes
Territory Management 2.0
Visual Workflow
Integration and Apex Utilities
Finishing Touches
Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Platform Cache Limits

The following limits apply when using Platform Cache.
Edition-specific Limits

The following table shows the amount of Platform Cache available for different types of orgs. To purchase more cache, contact your Salesforce representative.

Edition Cache Size
Enterprise 10 MB
Unlimited and Performance 30 MB
All others 0 MB
Partition Size Limits
Limit Value
Minimum partition size 5 MB
Session Cache Limits
Limit Value
Maximum size of a single cached item (for put() methods) 100 KB
Maximum local cache size for a partition, per-request1 500 KB
Minimum developer-assigned time-to-live 300 seconds (5 minutes)
Maximum developer-assigned time-to-live 28,800 seconds (8 hours)
Maximum session cache time-to-live 28,800 seconds (8 hours)
Org Cache Limits
Limit Value
Maximum size of a single cached item (for put() methods) 100 KB
Maximum local cache size for a partition, per-request1 1,000 KB
Minimum developer-assigned time-to-live 300 seconds (5 minutes)
Maximum developer-assigned time-to-live 172,800 seconds (48 hours)
Default org cache time-to-live 86,400 seconds (24 hours)

1 Local cache is the application server’s in-memory container that the client interacts with during a request.