How to check your resource usage on a VPS


This article shows how to view your resource usage on a VPS. Viewing this information on a Shared, Dedicated, or DreamPress hosting plan is not currently possible.

The following symptoms are often associated with high resource usage:

  • Out of memory
  • Restarts
  • Inability to log in (i.e., "ssh_exchange_identification: Connection closed by remote host")

Checking your daily and monthly resource usage

To check the daily and monthly memory usage graph in your panel, navigate to the Servers page and click the circular icon to the right of your server under the RAM column.

A graph opens that shows you the RAM Usage History.

This graph shows you a general overview of how much memory your VPS is using. Please note, however, that if a spike in memory occurred, it might not show on the graph since it only displays average usage.

Checking an overloaded VPS

If you've confirmed that your VPS is hitting its memory limits, it's recommended that you start out by doubling your current resource allocation to see if it's enough to prevent the VPS from rebooting. Once you've verified that things are running properly, you can reduce your resource allocation to the point where your peaks just barely exceed what you have allocated. Of course, you'll want to routinely monitor your usage and increase the resource allocation as your needs increase.

It's best to over-allocate than under-allocate! You don't want to discover that you've been under-allocated by your visitors/customers complaining about your sites not working properly.

You're only charged for the period that you have the slider in a particular position, so it's safe to experiment.

You will typically see Apache processes running on your server and appearing to consume all of the memory. This is generally not the case because Apache processes share a significant amount of memory. Additionally, DreamHost automatically configures Apache to work well within the memory allocation of your VPS.

It is still possible for a busy website to overwhelm a VPS server, but it is not generally the fault of the Apache web server itself. The processes you should be most concerned with are the PHP processes: PHP sites that are not optimized can use an extremely large amount of memory.

Of course, you may also want to try to reduce the server load, so you can reduce the resource allocation and save some money.

See also

Did this article answer your questions?

Article last updated PST.

Still not finding what you're looking for?