Performance

Diagnose and fix slow Mautic, high resource usage, and campaign delays.

Check current resource usage

bash
# Memory and CPU overview
free -h
docker stats --no-stream

Mautic dashboard is slow

  • Clear Mautic cache — go to Settings → System Info → Clear Cache, or run a container restart
  • Too many contacts — contact lists over 100,000 rows can slow the UI; archive old/inactive contacts regularly
  • MySQL performance — check MySQL logs for slow query warnings:
    bash
    sp logs mysql --tail 100
  • Low RAM — if RAM is consistently above 80%, upgrade your VPS tier

Email campaigns are delayed

Mautic sends emails through a queue processed by a cron job. If emails are delayed:

  • Check that Mautic's cron jobs are running (Mautic → Settings → System → Cron Jobs)
  • Check your SMTP provider's sending limits — you may be hitting rate limits
  • Increase cron frequency for higher sending volumes (contact support for configuration)

n8n workflows are slow

  • Split large batch workflows into smaller chunks
  • Use n8n's built-in Split In Batches node for processing large datasets
  • Schedule heavy workflows for off-peak hours (2–6 AM)
  • Increase PostgreSQL shared_buffers if pgvector queries are slow (contact support)

High disk I/O

bash
iostat -x 1 5

High disk I/O is usually caused by MySQL writing large transaction logs. On Starter-tier servers, moving to an NVMe SSD (Growth tier) makes a significant difference.

VPS upgrade checklist

  • RAM above 80% consistently → upgrade RAM
  • CPU above 70% consistently → upgrade CPU or move heavy n8n work to scheduled jobs
  • Disk above 70% → add storage volume or clean up old backups
  • Disk I/O consistently high → move to NVMe SSD storage
Backup & RestoreUpgrades