anchor.diff:  --J=-XX:+UseConcMarkSweepGC --J=-XX:CMSInitiatingOccupancyFraction=60
   ```
   
  +<a id="how_the_resource_manager_works"></a>
   ## Using the <span class="keyword">Geode</span> Resource Manager
   
   The <span class="keyword">Geode</span> resource manager works with your JVM's tenured garbage collector to control heap use and protect your member from hangs and crashes due to memory overload.
  
positive.code:  - Your choice of JVM
  Each JVM has its own GC behavior, which affects how efficiently the collector can operate, how quickly it kicks in when needed, and other factors.
  
  ## Resource Manager Example Configurations
  
  <a id="resource_manager_example_configurations__section_B50C552B114D47F3A63FC906EB282024"></a>
  
negative.code: 
  See also [Memory Requirements for Cached Data](../../reference/topics/memory_requirements_for_cache_data.html#calculating_memory_requirements).
  
  <a id="configuring_resource_manager"></a>
  ## Controlling Heap Use with the Resource Manager
  
  Resource manager behavior is closely tied to the triggering of Garbage Collection (GC) activities, the use of concurrent garbage collectors in the JVM, and the number of parallel GC threads used for concurrency.
  