As your project grows, you may need more processing power, memory, storage, or bandwidth than your current plan provides. Data Mammoth makes it easy to upgrade your server plan without losing data or rebuilding your environment. This guide walks you through the upgrade process, explains what happens during an upgrade, and covers important considerations.
When to Upgrade
Common signs that you need a plan upgrade:
- CPU usage is consistently above 80% during normal operations.
- RAM usage is high, and applications are swapping to disk.
- Disk space is above 85% full, even after cleanup.
- Response times are increasing for web applications or APIs.
- Traffic growth is pushing against bandwidth limits.
Understanding Plan Tiers
Data Mammoth offers several plan tiers, each with increasing resource allocations:
| Resource | What It Affects |
|---|---|
| vCPU Cores | Processing power for running applications, handling requests, and performing computations. |
| RAM | Memory available for active processes, databases, and caching. |
| Disk Space | Storage for your operating system, applications, databases, and files. |
| Bandwidth | Monthly data transfer allowance. |
How to Upgrade
What Happens During the Upgrade
- Brief downtime — Your server may need to restart during the upgrade process. Plan for a few minutes of downtime.
- Data preservation — All your files, configurations, applications, and databases are preserved.
- IP address — Your server's IP address does not change.
- Automatic resource allocation — The new CPU, RAM, and disk resources are applied automatically.
Downgrade Limitations
While upgrades are generally straightforward, downgrades may have limitations:
- Disk space — You cannot downgrade to a plan with less disk space than you are currently using. Free up space first or migrate data to external storage.
- Active add-ons — Some add-ons may not be available on lower-tier plans.
- In-progress billing — Downgrades typically take effect at the next billing cycle.
bash
df -hAnd clean up unnecessary files before requesting the downgrade.
Prorated Billing
When you upgrade mid-billing cycle, Data Mammoth calculates the prorated difference:
For example, if you upgrade halfway through a monthly cycle from a $10/month plan to a $20/month plan, you would be charged approximately $5 for the remaining half-month difference.
Preparing for an Upgrade
Before the Upgrade
After the Upgrade
bash
# Check CPU cores
nprocCheck available RAM
free -hCheck disk space
df -hAlternative to Upgrading
If you are not ready to upgrade your plan, consider these optimizations:
- Optimize your application — Review database queries, enable caching, and compress assets.
- Use a CDN — Offload static content delivery to reduce server load.
- Enable swap — Add swap space as a temporary memory buffer (not a permanent solution).
- Clean up disk — Remove old logs, unused packages, and temporary files.
- Optimize web server — Tune Apache or Nginx worker processes and connection limits.
What to Do Next
- Monitoring Server Performance — Track resource usage after the upgrade.
- Managing Server Add-ons — Enable additional services.
- Understanding Your Billing Cycle — Learn how prorated charges work.
- How to Cancel a Server — If you need to replace rather than upgrade.