anchor.diff:      ``` pre
       <cache>
       <region name="bigDataStore" refid="PARTITION_HEAP_LRU"/>
  -    ... 
  +    ...
       <resource-manager critical-heap-percentage="85" eviction-heap-percentage="75"/>
       </cache>
       ```
  
positive.code: 
      ``` pre
      Cache cache = CacheFactory.create();
                                      
      ResourceManager rm = cache.getResourceManager();
      rm.setCriticalHeapPercentage(85);
      rm.setEvictionHeapPercentage(75);
                                      
      RegionFactory rf = 
        cache.createRegionFactory(RegionShortcut.PARTITION_HEAP_LRU);
        Region region = rf.create("bigDataStore");
      ```
  
negative.code: -   The member hosting the region also runs an application that may take up to 1 Gb of the heap.
  -   The application must never run out of heap space and has been crafted such that data loss in the region is acceptable if the heap space becomes limited due to application issues, so the default `lru-heap-percentage` action destroy is suitable.
  -   The application's service guarantee makes it very intolerant of `OutOfMemoryException`s. Testing has shown that leaving 15% head room above the critical threshold when adding data to the region gives 99.5% uptime with no `OutOfMemoryException`s, when configured with the CMS garbage collector using `-XX:CMSInitiatingOccupancyFraction=70`.
  