Home
The Home page displays information on the overall status and performance of the server at any given time. If you logged in to the actual server, you would have access to this same information. This is view-only information.
If there are any system alerts that need your attention, they will be listed at the top of the screen.
When you log in to the control panel, the data provided is specific to the server IP address.
Health Check Results
You are presented with three levels of system health check:
- Degraded
- Warning
- Passed
Things to do in this section, include:
- You can expanded each section to view a list of health checks.
- Click Detailed Health Check or Full Health Check
FMOS memory health checks evaluate available memory rather than free memory.
- Click the icons
to open in a new window, download, or copy to clipboard.
Widgets on the page include:
- Load Average the maximum value is the number of CPUs with the last minute, 5 minutes and 15 minutes
- Memory displays how memory is being distributed
- Swap Memory displays the available virtual memory
System Status
The System Status, located in the upper right of the page, provides a quick visual look at the health of your server.
- Green—system is functioning properly
- Yellow—system is in maintenance mode
- Orange—system is degraded
- Red—system failure
- No color—not able to connect
Difference between available memory and free memory
Linux uses unused RAM for disk caching to improve system speed and responsiveness. This can make it look like very little memory is “free,” but this is normal and does not mean the system is low on RAM.
Disk caching temporarily uses memory that applications are not currently using. If an application needs more memory, the system automatically reclaims it from the cache immediately. This process happens seamlessly and does not negatively impact performance.
In most cases:
-
You do not need more RAM.
-
You do not need more swap space.
-
You do not need to disable disk caching.
Tools like top and free may show low “free” memory because Linux counts cached memory as used, even though it is readily available when needed. Cached memory is better understood as available memory.
In short, this behavior is expected, improves performance, and does not indicate a problem.
| Memory that is | You call it | Linux calls it |
|---|---|---|
| Used by applications | Used | Used |
| Used, but can be made available | Free (or available) | Available |
| Not used for anything | Free | Free |
A healthy Linux system with more than enough memory will, after running for a while, show the following expected and harmless behavior:
-
free memory is close to zero
-
available memory (or "free + buffers/cache") has enough room (let's say, 20%+ of total)
-
swap used does not change
Warning signs of a genuine low memory situation that you may want to look into:
-
available memory (or "free + buffers/cache") is close to zero
-
swap used increases or fluctuates