Troubleshooting Performance Issues in Joget with Application Performance Monitoring (APM)

When facing performance issues without clear indicators, follow this systematic diagnostic approach to isolate and resolve the root cause.

Step 1: Identify the Pattern

Determine the scope of the issue:

• System-wide

  • APM (Application Performance Monitoring) may not be helpful.
  • Focus on infrastructure-level metrics instead.

• App-specific or Action-specific

  • Use APM to extract slow traces for targeted analysis.

Step 2: Collect System-Level Data

Gather baseline diagnostics:

• Navigate to System Settings > System Info

  • Capture JVM specs, memory allocation, and environment details.

• Access APM > Server Stats > JVM Performance Tab

  • Set the range to last 24 hours for trend analysis.

Step 3: Analyze Resource Utilization

Check for anomalies in memory and CPU:

• Memory Leak or Excessive Usage

  • If memory usage is unusually high or growing over time, generate a heap dump.

• High CPU Usage

  • Capture a thread dump to identify bottleneck threads.

Step 4: Deep Dive into APM Slow Trace (App/Action Specific)

Use APM to inspect specific slow actions:

• Duration

  • Identify how long the action took.

• URL & Request Parameters

  • Understand the context (e.g., form submission, list loading, assignment completion).

• Breakdown

  • Pinpoint which execution stage consumed the most time.

• JVM Thread Stats

  • Identify which components are heavily occupied.

• Query Stats

  • If the issue is query-related, analyze SQL performance.
  • Otherwise, this section can be skipped.

• Profile Tab

  • Always review for method-level performance insights.

What APM Cannot See

Some performance factors are outside APM’s visibility:

• Disk I/O

  • Dependent on infrastructure (e.g., Kubernetes).
  • Request an infra-level performance breakdown.

• Database Specification

  • Obtain database specifications and table storage breakdown for in-depth analysis.

Summary Checklist