Linux Check Memory Slots Used

Posted on by admin

It is essential that your Linux system runs at an optimal level. A few simple terminal commands provide access to all relevant information and help you monitor memory statistics.

In this tutorial, learn five powerful commands to check memory usage in Linux.

We also provide detailed explanations of what they do and more importantly, how to interpret the results. The commands will work with nearly all Linux distributions. In this instance, the commands and the results are presented using Ubuntu 18.04

  • Access to a command line / terminal
  • User with sudo privileges
  • The apt package manager
Linux check memory slots used cars

Total used free shared buffers cached Mem: 802 0 1004 -/+ buffers/cache: 23856 Swap: 1564 top. Check our excelent post to understand Linux top command output. Output: cat /proc/meminfo.

  • When troubleshooting system or application slowdown or misbehavior, one of the first things to check is the system memory usage. This article explains how to check RAM usage in Linux using several different commands. Free Command # free is the most commonly used command for checking the memory usage of a Linux system. It displays information.
  • Free displays the total amount of free and used physical and swap memory in the system, as well as the buffers and caches used by the kernel. The information is gathered by parsing /proc/meminfo. Suggested Read: free – A Standard Command to Check Memory Usage Statistics (Free & Used) in Linux.
  • By far the easiest way to check the number of RAM slots currently in use in your machine without opening it up is to use the DMI Table Decoder command called dmidecode, which gives you a flat report. At the command prompt, type sudo dmidecode -t 16 and push enter. You’ll probably be asked for your administrator password.

Entering cat /proc/meminfo in your terminal opens the /proc/meminfo file.

Linux Check Memory Slots Used To

This is a virtual file that reports the amount of available and used memory. It contains real-time information about the system’s memory usage as well as the buffers and shared memory used by the kernel. The output might differ slightly based on the architecture and operating system in question.

This is an example of what the /proc/meminfo file looks like in Ubuntu 18.04:

The terminal displays the information in kilobytes.

free Command to Display the Amount of Physical and Swap Memory

Typing freein your command terminal provides the following result:

The data represents the used/available memory and the swap memory figures in kilobytes.

totalTotal installed memory
usedMemory currently in use by running processes (used= total – free – buff/cache)
freeUnused memory (free= total – used – buff/cache)
sharedMemory shared by multiple processes
buffersMemory reserved by the OS to allocate as buffers when process need them
cachedRecently used files stored in RAM
buff/cacheBuffers + Cache
availableEstimation of how much memory is available for starting new applications, without swapping.

Compared to the /proc/meminfo file, the free command provides less information. However, it is easier to understand. The key figure being the available value as it displays how much memory is still available for running new applications.

The free command has multiple options to format the output so that it better matches your requirements. The table below lists the most useful variations of the free command.

OptionsResult
-boutput in bytes
– koutput in kilobytes
– moutput in megabytes
– goutput in gigabytes
– ldetailed low and high memory statistics
– oold format (no -/+buffers/cache line)
– ttotal for RAM + swap
– supdate every [delay] seconds
– cupdate [count] times

Note: As with most commands, entering man free displays an overview of all variations and descriptions of the results.

vmstat Command to Report Virtual Memory Statistics

The vmstatcommand is a useful tool that reports virtual memory statistics.

vmstat provides general information about processes, memory, paging, block IO, traps, and CPU activity.

The detailed description listed below provides an explanation for each value in case you need assistance in analyzing the results.

  • Procs
    • r: number of processes waiting for run time.
    • b: number of processes in uninterruptible sleep.
  • Memory
    • swpd: amount of virtual memory used.
    • free: amount of idle memory.
    • buff: the amount of memory used as buffers.
    • cache: amount of memory used as cache.
  • Swap
    • si: memory swapped in from disk (/s).
    • so: memory swapped to disk (/s).
  • IO
    • bi: Blocks received from a block device (blocks/s).
    • bo: Blocks sent to a block device (blocks/s).
  • System
    • in: number of interrupts per second, including the clock.
    • cs: number of context switches per second.
  • CPU – These are percentages of total CPU time.
    • us: Time spent running non-kernel code. (user time, including nice time)
    • sy: Time spent running kernel code. (system time)
    • id: Time spent idle. Before Linux 2.5.41, this includes IO-wait time.
    • wa: Time spent waiting for IO. Before Linux 2.5.41, included in idle.
    • st: Time stolen from a virtual machine. Before Linux 2.6.11, unknown.

The top command is useful to check memory and CPU usage per process. It displays information about:

  • uptime
  • average load
  • tasks running
  • number of users logged in
  • number of CPUs/CPU utilization
  • memory/swap system processes

The data is continuously updated, which allows you to follow the processes in real-time.

Aside from providing you with essential memory information, the top command provides a limited interactive interface. It is possible to manipulate and configure operations by using command-line options.

The man top command provides a comprehensive list of all available variations.

The information the htop command provides is similar to the top command. However, the real advantage to the htop command is its user-friendly environment and improved controls.

Slots

The command uses color for its output, provides full command lines for processes, as well as the option to scroll both vertically and horizontally.

The following output appears:

Linux Check Memory Slots Used Car Dealers

    1. The top segment provides summary information and contains graphic meters and text counters.
    2. The lower section structures the detailed data, per process. This allows you to perform actions on individual processes with ease.
    3. The shortcuts listed at the bottom of the screen will enable you to manipulate and customize the processes quickly and without the need to type specific commands.

Note: If you run into “Command ‘htop’ not found” message when trying to run the htop command, you will need to install the htop function first:

As an alternative, use the command below:

Using a graphical interface for server administration is not common practice. However, certain data sets are much clearer, with a visual representation of memory usage.

To access the System Monitor:

  1. Navigate to Show Applications.
  2. Enter System Monitor in the search bar and access the application.
  3. Select the Resources tab.
  4. A graphical overview of your memory consumption in real time, including historical information is displayed.

This guide provided several options to check memory usage on your Linux system. We learned that a single command provides an abundance of valuable data for future analysis. Learning to interpret the information correctly is critical.

Now you can administer your server more efficiently.

Next you should also read

This tutorial shows how to display disk usage from a command line in Linux. It is important to know how much…

The Linux kernel is much like the central brain of the operating system. Although it is open-source – meaning…

There are many different tools for monitoring network traffic on a Linux server. Each option has its…

Linux Check Memory Slots Used Cars

Reducing server response time to the bare minimum is one of the primary goals of website owners and SEO…

You have probably noticed your Linux OS slowing down, especially when working harder. Understanding CPU…