Skip to content

Panel

The Panel page exposes the AcePanel process's own Go runtime statistics and live goroutine stack traces. It is mainly useful for diagnosing the panel itself, for example when investigating memory growth, garbage collection behavior, or stuck goroutines.

You can open it from the Toolbox, then select the Panel tab. The page is split into two sub-tabs: Runtime and Goroutines. The Runtime sub-tab is shown by default.

TIP

All data on this page describes the AcePanel backend process (ace) itself, not your websites, databases, or other applications. To inspect arbitrary system processes, use the Process Management page instead.

Runtime

The Runtime sub-tab reads the panel process's runtime and memory statistics on demand. Click Refresh in the Basic Info header to reload all values.

The data is grouped into the following sections.

Basic Info

FieldDescription
UptimeHow long the panel process has been running
GoGo version the panel was built with
GoroutinesCurrent number of running goroutines
CPU CoresNumber of logical CPUs available to the process
Cgo CallsTotal number of cgo calls made by the process

Memory

General memory statistics for the process.

FieldDescription
AllocatedBytes of allocated heap objects currently in use
Total AllocatedCumulative bytes allocated for heap objects over time
SystemTotal bytes of memory obtained from the operating system
LookupsNumber of pointer lookups performed by the runtime
MallocsCumulative count of heap objects allocated
FreesCumulative count of heap objects freed

Heap

Detailed heap allocation statistics.

FieldDescription
AllocatedBytes of allocated heap objects currently in use
SystemBytes of heap memory obtained from the system
IdleBytes in idle (unused) heap spans
In UseBytes in in-use heap spans
ReleasedBytes of physical memory returned to the OS
ObjectsNumber of allocated heap objects

Stack / MSpan / MCache

Statistics for stack memory and the runtime's internal allocator structures.

FieldDescription
Stack In UseBytes in use by stack spans
Stack SysBytes of stack memory obtained from the system
MSpan In UseBytes of allocated mspan structures
MSpan SysBytes obtained from the system for mspan structures
MCache In UseBytes of allocated mcache structures
MCache SysBytes obtained from the system for mcache structures
BuckHash SysBytes used by the profiling bucket hash table
Other SysBytes of memory used for other runtime allocations

GC

Garbage collection statistics.

FieldDescription
GC RunsTotal number of completed GC cycles
Forced GC RunsNumber of GC cycles forced by the application
GC Pause TotalCumulative time spent in stop-the-world GC pauses
Last GCTimestamp of the most recent garbage collection
Next GC TargetHeap size target that will trigger the next GC
GC SysBytes of memory used for GC metadata
GC CPU FractionFraction of total CPU time used by the GC, shown as a percentage

TIP

Memory and heap values are displayed in human-readable units (B, KB, MB, GB, TB). Durations and GC pause times are formatted automatically (for example ns, us, ms, or s), and uptime is shown as days, hours, minutes, and seconds.

Goroutines

The Goroutines sub-tab dumps the full stack trace of every goroutine currently running inside the panel process.

For performance reasons this data is not loaded automatically. It is fetched the first time you open the sub-tab, and you can reload it at any time with the Refresh button. A counter at the top shows the total number of goroutines (Total: N).

Each goroutine is listed as a collapsible item showing:

  • State: the goroutine's scheduler state (for example running, IO wait, select, chan receive). Goroutines in the running state are highlighted.
  • goroutine ID: the runtime-assigned goroutine identifier.

Expand an item to view the goroutine's full stack trace, rendered as Go source for readability.

TIP

This view is primarily a debugging aid. A large or steadily growing number of goroutines may indicate a leak and is useful information when reporting an issue.

Notes

  1. This page reflects the internal state of the AcePanel process and is intended for diagnostics, not routine administration.
  2. The values are point-in-time snapshots taken when the page is loaded or refreshed; they are not updated live.
  3. Capturing all goroutine stacks briefly pauses the runtime, so avoid refreshing the Goroutines sub-tab repeatedly on a busy server.