Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Troubleshooting

Server memory usage: how to read RAM pressure

Published August 2026 · 8 min read

Linux tries to use otherwise-idle memory for useful caching, so a server showing little “free” RAM can still be healthy. The important signals are available memory, swap behaviour, memory pressure, process growth, latency, and out-of-memory events.

Look at available memory, not only free memory

Filesystem cache can be reclaimed when applications need memory. A low free number by itself is less meaningful than whether the system has reclaimable cache and enough available memory to satisfy normal work.

Check which processes are growing

Sort by resident memory and compare with normal baselines. Application workers, databases, Java runtimes, container workloads, image processing, caches, and runaway processes can each have different expected patterns.

Treat swap and OOM events as evidence

Some swap use can be normal, but sustained heavy swapping with slow response suggests pressure. Kernel OOM kills are stronger evidence that the system could not satisfy allocations and terminated a process to recover.

Scale only after understanding the workload

More RAM is the correct fix when healthy normal demand exceeds capacity. It is not the correct first response to a memory leak, unbounded queue, misconfigured worker count, or one broken request consuming excessive memory.

Next step

High server memory usage is not automatically a problem. Learn free vs available memory, cache, swap, OOM kills, process growth, and how to tell normal caching from real pressure.

Compare VPS resources

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

cPanel error logs: where to look when a site breaks

cPanel exposes recent website errors, while server and application logs may contain deeper detail. Learn which log to check for PHP, Apache, cPanel, mail, and system failures.

Read the guide

Database connection failed: how to check the whole path

A database connection failure can involve DNS, host, port, firewall, service state, TLS, credentials, privileges, connection limits, or application configuration.

Read the guide

More troubleshooting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move