How do I monitor my CPU and RAM usage in cPanel?

At Hodi, every web hosting plan has allocated resources: computing power (CPU), memory (RAM), disk access, etc. These resources guarantee the stability and performance of our infrastructure, preventing one site from affecting the others.

If your activity increases (more visitors, heavier scripts, e-commerce, etc.), you can increase your resources by changing your hosting plan.

The "Resource Usage" section in cPanel lets you track your consumption precisely, so you know exactly where you stand before considering any changes. Click "Current usage" to view your usage in detail.

Processor Usage (CPU Usage)

CPU is your server's computing power: everything your site "runs" (PHP, queries, processing) consumes it.

What does this graph show?

• Green line (average): your average CPU consumption.
• Red line (limit): the maximum limit allowed by your plan.
• Blue line (database): the share related to your database.
• Light vertical marks (faults): the moments when the limit was reached.

How to interpret it?

• ✅ The green line stays well below the limit → everything is fine, you have headroom.
• ⚠️ It regularly touches the red line → your site is reaching its limit.
• 🔴 You see frequent "faults" → some requests are being slowed down or blocked.

Memory (Physical Memory Usage)

RAM is working memory: it temporarily stores what your site is handling at any given moment.

What does this graph show?

• Green line: memory used.
• Red line: your plan's RAM limit.

How to interpret it?

• ✅ The green line stays well below the limit → everything is fine.
• ➖ It touches the limit from time to time → normal during a one-off heavy processing task.
• 🔴 It regularly touches the red line → requests are being blocked, which can cause 503 errors.

Resource overruns (Faults) and common causes

A "fault" is a moment when your site reached one of its limits. Here are the main types and what they indicate:

• CPUf: processor limit reached.
• PMemF: RAM limit reached.
• NprocF: too many simultaneous processes (often the consequence of an overrun on another resource).
• IOf: disk I/O limit (the disk read/write throughput).
• IOPSf: too many disk operations per second.

A few isolated spikes are normal. Repeated spikes, however, indicate either a need for optimization or a plan that is undersized for your activity.

The most common causes of a resource overrun are:

• resource-heavy plugins or modules (WordPress, e-commerce, etc.);
• the absence of caching;
• large imports/exports;
• heavy database queries;
• scheduled tasks (cron jobs) that run too often;
• a traffic spike generating many simultaneous PHP processes.

So how do you actually find out what's causing it?

Your developer can use a tool like PHP X-Ray, available in cPanel, to precisely analyze what is consuming time and memory: slow SQL queries, resource-heavy plugins, expensive PHP functions, calls to external services, or scripts running too often.

This type of analysis makes it possible to pinpoint the exact saturation point and adjust the code or configuration before considering an upgrade. And if the need is real, changing your plan gives you more headroom, with complete peace of mind.

Updated on: 17/07/2026