Upgrade to a bigger plan when you need more resources

Learn the signs that your server needs more RAM, CPU or disk, how to confirm it with simple commands, and how to move to a bigger RunRacks plan or ask support about an upgrade.

  • Beginner
  • All
  • 5 min read

By RunRacks Team · Published

Servers grow. A site gets more visitors, you add another trading terminal, or a database doubles in size. At some point the plan you started on is no longer enough. This guide shows how to tell whether you really need more resources, how to measure it, and the two ways to get a bigger RunRacks plan.

Before you start

  • You can log in to the server over SSH (Linux) or Remote Desktop on port 12230 (Windows).
  • You are signed in to the Dashboard.
  • A recent backup of anything important. Any change of plan is a good moment to have one.

Signs you are running out of resources

Memory (RAM)

  • Apps crash or restart without a clear error.
  • On Linux, the kernel log mentions the OOM killer ("Out of memory: Killed process").
  • On Windows, you see "Your computer is low on memory" warnings, or the desktop becomes slow when you open one more program.

CPU

  • The server feels slow even with little memory in use.
  • CPU sits near 100% for long periods, not just short spikes during updates or backups.

Disk

  • Free space keeps shrinking and you are below about 10–15% free.
  • Writes fail with "No space left on device" (Linux) or Windows warns that a drive is full.

A short spike is normal. What matters is a steady pattern over days, at the times you care about.

Measure before you upgrade

Upgrading fixes a real shortage, but not a runaway process or a log file that fills the disk. Check first.

On a Linux VPS

Terminal
free -h

Look at the available column. If it is close to zero most of the time and swap is in heavy use, you are short of memory.

Terminal
top

Press P to sort by CPU and M to sort by memory, then q to quit. Note which process uses the most.

Terminal
df -h

Check the Use% column for /. Above 85–90% needs attention.

On a Windows VPS or Admin RDP

Open Task Manager (Ctrl + Shift + Esc), choose More details if needed, and look at the Performance tab for CPU, Memory and Disk. The Processes tab shows what is using the most.

In PowerShell, check free disk space:

PowerShell
Get-PSDrive -PSProvider FileSystem

Rule out simple fixes

  • A single process using far more than it should may have a bug or a memory leak. Restarting or updating it may solve the problem.
  • Old logs, backups and downloads often fill the disk. Clear them before paying for more space.
  • Too many startup programs on a Windows desktop use RAM all day. Remove those you do not need.

If the shortage is still there after that, you have outgrown the plan.

Option 1: order a bigger plan and move

The most predictable path is to order a larger plan and move your data across:

  1. Pick a plan with more resources on Pricing. Choose the same location if you want to keep latency the same for your users.
  2. Add it to the cart and check out. The new server appears under Services with its own IP address and login details.
  3. Set up the new server and copy your data and settings across.
  4. Test everything on the new server while the old one still runs.
  5. Switch over: update DNS records, or point your apps and users at the new IP address.
  6. When you are sure everything works, cancel the old service.

The big advantage is that your old server stays untouched until the new one is proven. Moving to a new server: plan your migration covers each step in detail.

Option 2: ask support about an upgrade

If you would rather keep your current server and IP address, ask support whether an in-place upgrade is possible for your service:

  1. Open a ticket and choose the related service.
  2. Say which plan you are on now, which resource you need more of, and what you measured.
  3. Ask what options exist, what it costs, and whether the server needs a restart.

Support will tell you what is possible for that service and how billing works. Do not assume a price or a downtime window until they confirm it.

Check it works

After moving or upgrading, run the same checks as before:

  • Linux: free -h, nproc (shows the number of CPU cores) and df -h.
  • Windows: Task Manager → Performance.

The totals should match the new plan, and the shortage you saw before should be gone under the same workload.

Troubleshooting

  • Still slow after upgrading: the bottleneck was something else, such as a slow database query or an app setting. Measure again to find it.
  • Disk total did not grow after an upgrade on Windows: the extra space may be unallocated. It needs extending in Disk Management.
  • Apps on the new server cannot reach a database or API: an allow-list still has the old IP address. Update it.
  • Unsure which plan to choose: RunRacks AI can help you size a plan from your measurements.

Next steps

Was this guide helpful?

Still stuck?

Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.

Billing & account

Cancel a service with a cancellation request

How to cancel a RunRacks server with a cancellation request, what to back up first, how to choose when it ends, and where to read the terms and refund policy.

  • Beginner
  • All
  • 4 min read

Billing & account

Pay an invoice in the RunRacks Dashboard

Find unpaid invoices in the RunRacks Dashboard, open one, pay it with one of the methods offered, and confirm it now shows as paid.

  • Beginner
  • All
  • 4 min read

Billing & account

What happens when an invoice is overdue

A plain explanation of overdue invoices, why an unpaid renewal can put your service at risk of suspension, how to pay quickly, and where to read the exact rules in the RunRacks terms.

  • Beginner
  • All
  • 5 min read