How to Check VPS Resources Usage at Hostinger

Learn where to check the usage of your VPS resources

Updated 2 weeks ago

Checking VPS resources usage

Navigate to the VPS section on hPanel and click Manage next to your chosen server. Then, open the Backups & Monitoring section on the left side panel and click on Server Usage:

VPS Hostinger sidebar, Server Usage selected

Choose the period you’d like to analyze: the last 24 hours, week, month, or year:

Hostinger VPS resources view with the Last 24 hours tab selected

Below, you’ll find several graphs with the main VPS metrics.

The graphs in the Server Usage section use the GMT+0 timezone 💡

CPU usage

CPU usage displays the amount (in %) of CPU power consumed by your server:

VPS CPU usage line chart with periodic spikes over time

It’s completely normal if CPU usage is high from time to time. It can increase when you’re installing resource-heavy applications or when your VPS is processing a lot of data.

When you see that your CPU usage keeps increasing, you can find the processes that cause the high usage and use our VPS AI Assistant to get insights on how to address the cause.

CPU usage dashboard showing recent spikes and a table of resource-heavy commands

RAM usage

RAM usage displays the amount of memory (GB) that’s used by your server’s processes:

VPS RAM usage chart showing a drop from 2 GB to about 1.5 GB over time

RAM and PHP memory are not the same. To learn more about it, check this article: What Is the Difference Between PHP Memory Limit and RAM? 💡

Number of processes

This graph displays the total number of all processes running on your server:

VPS resource usage chart for number of processes over time

We recommend keeping the number of processes low. For shutting down any process, you can refer to this tutorial: How to Kill a Process in Linux 💡

Disk space

Disk space shows the amount of data (GB) held in the disk of your server:

VPS disk space usage chart showing a steady line near 2 GB

If you notice your disk usage is high, you can investigate further via SSH. The following commands help identify what is consuming disk space:

Check overall disk space:

df -h

This shows total, used, and available space for each mounted filesystem.

Find the largest directories:

du -sh /* 2>/dev/null | sort -rh | head -20

Lists the top 20 directories by size, starting from the largest.

Find large files in a specific directory:

du -sh /var/log/* | sort -rh | head -10

Useful for spotting oversized log files, which are a common culprit.

In case you are worried about disk space, you may enable disk quota and limit the amount of space your files take.

VPS dashboard warning: disk usage has reached 100%, with a highlighted Free up space button

Disk inodes

Inodes are items that correspond to the number of files and folders you have on your server:

VPS resource graph showing disk inodes usage over time
You can also check it further from SSH.

Check inode usage per filesystem:

df -i

High inode usage (even with free disk space) can cause “disk full” errors. This is especially common when log files or cache files accumulate as many small files.

Find directories with the most files (inode-heavy):

find / -xdev -printf '%hn' 2>/dev/null | sort | uniq -c | sort -rn | head -20

It’s crucial to keep the number of inodes low. Unattended files (e.g., log files that are being generated on a regular basis) can fill up your disk space pretty fast.

Outgoing traffic

Outgoing traffic shows connections from the server to a remote location:

VPS outgoing traffic chart showing network usage over time

Incoming traffic

Incoming traffic shows connections coming into the server from a remote location:

VPS Incoming traffic graph showing spikes around 3–5 PM and 6–8 AM

Reducing VPS resources usage

High usage of your VPS resources usually comes down to poor website optimization. This can be solved by considering the following aspects:

The physical distance between you and the server

The bigger the distance between you and the server your website is hosted, the longer response time you may expect. To solve this, we recommend you set up a CDN or content delivery network. It works by keeping multiple copies of your website’s data in proxy servers worldwide, thus improving your website speed for visitors, no matter their physical location.

Although, for instance, if you and your target audience are from the USA, and your server is in Asia, a CDN might not help much. Instead, you may contact the Hostinger Customer Success team, and request transferring your hosting to a closer location.

Poor optimization of database queries

Optimizing how queries are made, seeking only the essential data, or limiting the query results is the way to go when it comes to query optimization. There are tools that help in this matter, e.g., EverSQL. Additionally, you may find useful information in various forums or blog posts, like this one: Supercharge Your SQL Queries for Production Databases 💡