1. Administration Guide
  2. Understanding Resource Utilization and Performance

Understanding Resource Utilization and Performance

This section discusses:

  • Requirements

  • Configuration Setup

The EnterpriseOne Kernel can sometimes encounter certain complex issues which have proved intractable to resolve. Some of these intractable issues are Kernel Crashes, Deadlocked UBEs, or Out-of-Memory conditions that require specialized code to determine the root cause. In addition, the kernel and batch processes utilize resources and place demands on memory and the CPU and execute in the context of other processes that also demand memory and CPU resources. Each process has its own level of impact on the system, and the cumulative effect of all processes currently running will impact performance. Appropriate data can be captured and used with measurement tools to evaluate overall performance as well as the impact of individual processes. When utilization or performance exceeds certain thresholds, it is critical to have tools that can diagnose which process is creating the resource overload in order to correct the problem and restore the performance to normal levels before the system crashes.

A new administration tool called Kernel Resource Management (KRM) has been added to Server Manager to enable you to isolate and determine root causes of CPU and Memory issues, increase system stability and simplify the troubleshooting process. Graphs allow you to quickly identify processes with high resource consumption and recycling allows the ability to reclaim system resources.

There are graphs for the following:

  • Summary Graphs for entire Enterprise Server that displays memory and CPU usage.

  • At Enterprise Server level, there are graphs that display the Top 10 Processes by Memory and CPU.

  • At the Individual Process Level there are graphs for CPU, Memory, caches and DB connections.

New diagnostics allows you to quickly identify root cause of resource consumption issues. For Diagnostics, information about the current resource usage is written to the jdedebug.log:

Cache information:

  • Cache name

  • Number of records in the cache

  • Indices

Database Transactions:

  • Commitment type

  • User

  • Application

KRM enables you to monitor kernel and batch processes and to diagnose CPU and memory usage issues.