Admin Guide
Performance monitoring
View real-time server resource usage and run system maintenance tasks
View real-time server resource usage and run system maintenance tasks. Sign in with the Root account, open the system settings page (`/console/setting`) and find the "Performance monitoring" tab. The web console follows the reference design and is still being wired up.
Run maintenance tasks
Cleanup mode
Performance monitoring
Request body disk cache
0 Bytes / 1 GB
Request body memory cache
Current cache size: 0 Bytes
Cache directory disk space
Used: 2.44 GB · Free: 953.2 GB · Total: 1000.95 GB
- Allocated memory10.57 MB
- Total allocated memory222.43 MB
- System memory51.66 MB
- GC runs252
- Goroutines23
- Cache directory/tmp/new-api-body-cache
- Files in directory0
- Directory size0 Bytes
Performance monitoring tab preview: log cleanup, maintenance buttons, cache panels and Go runtime metrics
Open performance monitoring
After signing in as Root, open /console/setting and switch to the "Performance monitoring" or "Performance settings" tab. The page shows the gateway process's resource usage as read-only data. Maintenance actions take effect immediately on the running EasyAPI service, so run them during off-peak hours.
Clean up log files
Choose whether to keep logs by file count or by days, enter the threshold and click "Clean up log files". This cannot be undone, so back up or make sure the logs are archived first.
| Cleanup mode | Description |
|---|---|
| Keep the latest N files | Keep the newest logs by file count and delete the rest |
| Keep the last N days | Delete log files older than the time window |
Maintenance buttons
| Action | Description |
|---|---|
| Refresh stats | Reload real-time metrics such as memory, GC, cache and disk usage |
| Clear inactive cache | Free entries in the request body disk/memory cache that have not been accessed for a long time |
| Reset stats | Reset cumulative counters such as hit rate so you can observe a fresh round of traffic |
| Run GC | Manually trigger Go runtime GC (recommended only when investigating memory during off-peak hours) |
"Run GC" briefly increases CPU usage; "Reset stats" only resets the counters and does not touch cached files.
Request body cache
EasyAPI uses a two-tier disk + memory cache for large request bodies to save bandwidth on repeated uploads. The disk cache directory lives in a temporary path by default (e.g. /tmp/new-api-body-cache), and its usage is tracked by the "Cache directory disk space" progress bar.
- Request body disk cache: 0 Bytes / 1 GB
- Request body memory cache: Current cache size: 0 Bytes
- Cache directory disk space: Used: 2.44 GB · Free: 953.2 GB · Total: 1000.95 GB
Runtime statistics
The metrics below come from the Go runtime and help you spot memory or goroutine leaks:
| Metric | Sample value |
|---|---|
| Allocated memory | 10.57 MB |
| Total allocated memory | 222.43 MB |
| System memory | 51.66 MB |
| GC runs | 252 |
| Goroutines | 23 |
| Cache directory | /tmp/new-api-body-cache |
| Files in directory | 0 |
| Directory size | 0 Bytes |
Related
- For an overview of the System settings tabs, see System settings
- For pprof / Pyroscope integration on the deployment side, see Performance profiling setup guide
- Channel response times are shown in the response_time column of the Channel management list
- Only Root (role=100) can access the Performance monitoring tab