You are here:
Request a Platform Cache Trial
To test performance improvements by using Platform Cache in your own org, you can request trial cache for your production org. Enterprise, Unlimited, and Performance editions come with some cache, but adding more cache often provides greater performance. When your trial request is approved, you can allocate capacity to partitions and experiment with using the cache for different scenarios. Testing the cache on a trial basis lets you make an informed decision about whether to purchase cache.
Salesforce approves trial cache requests immediately and sends you an email to notify you that your Platform Cache trial is active. It can take a few minutes for you to receive the email. You receive 30 MB of trial cache space (10 MB if you have Developer Edition). If you need more trial cache space, contact Salesforce.
After you request trial cache, you receive emails at the following intervals.
| Email Timing | Action Required |
|---|---|
| At activation | You can now allocate capacity to partitions and test the trial cache in your org. |
| Three days before expiration | Before expiration, be sure to reconfigure your partitions to deallocate the added trial space. |
| At expiration | The trial cache is removed from your org. |
Developer Edition Orgs
You can request trial cache for a Developer Edition org. After you sign up for the org, request trial cache from the Platform Cache Partition tool. ISVs who are using Developer Edition orgs to create managed packages can get 10 MB of trial cache for up to two Developer Edition orgs. ISVs can contact their Salesforce representative to get trial cache in Developer Edition orgs.
Cache Reduction Algorithm
At the end of your trial period, Salesforce removes the granted trial cache space from your org. Before your trial ends, make sure that you’ve deallocated your trial cache space. You can deallocate space from the Platform Cache Partition tool by resetting partition allocations. If you don’t deallocate the cache space, Salesforce removes the granted cache using the following process.
- The system removes cache from the smallest non-default partition first.
Note The size of a partition is the total allocation for the partition, which includes org-wide cache and namespace-specific cache. - The system then works its way through the partitions from smallest to largest in size. If multiple partitions have the same size, the system proportionally removes cache from these partitions.
- The system reduces partitions to a minimum size of 5 MB, unless all the trial cache space can’t be removed. In this case, partitions are reduced to 0 MB.
- The default partition (if it exists) is reduced last only if the trial cache space can’t be removed from all other partitions.
If unallocated space is present:
- If the amount of unallocated space is greater than the amount of space that must be removed, the system removes only unallocated space.
- If the amount of unallocated space is less than the amount of space that must be removed, the system removes the unallocated space first. The system then follows the cache reduction process to remove the remaining amount.
