Memory Usage Statistics

Introduction

Memory Usage Statistics is an FNZ Studio Composition option that allows you to avoid stability and performance issues caused by high memory consumption. Especially for Solution Engineers, knowing how memory consumption is distributed is essential to optimize the developed solution. In fact, this information can help them in tasks such as: tune configuration options (such as eviction, near caches, and so on), use the right components, cache only the necessary data.

memory Usage Statistics are available in: System Maintenance > Statistics > Memory Usage Statistics.

Memory Holders User Interface

The concept behind Memory Usage Statistics is to identify the areas in which data is stored for a long period of time (e.g. Distributed Maps, Application Caches, and so on) and compute their sizes. In order to collect this data, a feature called Memory Holder is implemented. The following information is available on the Memory Usage Statistics page in FNZ Studio:

• Memory Holders tab: information such as the Memory Holder name (Distributed Maps, etc.); date and time at which the memory data was last updated; amount of memory taken, and so on.
• Memory Pools tab: memory area where data is stored. The information available here is:
  • Used memory: amount of memory currently used.
  • Committed memory: amount of memory that is guaranteed to be available by the Java virtual machine.
  • Max memory: maximum amount of memory that can be used for memory management.

Note: Old Generation is where data is stored for the longest time.

• Unaccounted Memory Usage tab: amount of memory represented by the difference between the size of the Old Generation and the total memory that was computed. The data displayed is not computed in real time. The Memory Usage job computes and caches this data every hour. However, you can run this job manually if you want to see updated data.