Cache.org.getCapacity() returns incorrect results of org cache usage
Trailblazer Community

Cache.org.getCapacity() returns incorrect results of org cache usage

Platform

Last updated 2 days ago ·Reference W-4839559 ·Reported By 1 users

Fixed - Summer '20

Summary
Cache.org.getCapacity() returns incorrect results of org cache usage. We see that it returns 5 times its actual cache usage.

Repro
Try to turn on the trial cache capacity if it is not already turned on and make sure that the partition that you create is a default partition if you don't have one already ( ** This is for a vanilla org where partition cache is not used before )

- Create a partition in the org (namespace-local';partition-'GSO') and allocated a minimum 5MB capacity to the session and org cache.
- Run the following piece of code to populate 20 key-value pairs to the org cache from dev console.

for(Integer i=5;i<20;i++){
DateTime dt = DateTime.parse('03/'+i+'/2018 01:40 PM');
Cache.Org.put('local.GSO.orderDate' + i, dt);
if (Cache.Org.contains('local.GSO.orderDate' + i)) {
DateTime cachedDt = (DateTime)Cache.Org.get('local.GSO.orderDate' + i);
}
}
- Notice that the chart 'Org Cache Usage' in the partition cache page and also the one in the 'Org Cache Diagnostics for Partition' page correctly shows the org cache usage ( 2.37KB ) which is only around 0.04% of the total allocated org cache of 5120KB.

- Next, try to run the following method to get the capacity from dev console system.debug('@@Cache Capacity: '+cache.org.getCapacity());

- In the debug logs it is seen that the cache capacity shows 0.2% which means it uses 10KB which is 5 times the actual utilization.

Workaround
- Customers can try using org level capacity = getCapacity()/orgCachePartitionSizeInMB in their cache implementation logic but they need to revert this back once the bug is fixed.

Reported By (1)

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP28 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS12 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS123 CS137 CS138 CS13 CS133 CS132 CS14 CS148 CS142 CS15 CS152 CS151 CS165 CS16 CS169 CS17 CS18 CS194 CS19 CS198 CS196 CS195 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS30 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS93 CS94 CS95 CS96 CS97 CS98 CS99 EU7 EU8 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA130 NA134 NA133 NA136 NA135 NA132 NA131 NA146 NA142 NA141 NA154 NA155 NA172 NA174 NA171 NA173 NA196 NA21 NA37 NA39 NA44 NA45 NA46 NA47 NA49 NA52 NA54 NA57 NA58 NA59 NA61 NA62 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.