Linux Memory Slots Info certainly can! Internet casinos normally offer US players the chance to gamble in US Dollars, Canadian Dollars, Euros, Great British Pounds Linux Memory Slots Info and other legal tender. Some also offer gaming in dozens of other currencies as well. In this way, you can deposit funds and collect winnings in your local.
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.
You can use memtester once booted into linux. Sudo memtester 1024 5 This should allocate 1024MB of memory, and repeat the test 5 times. – Ricky Hewitt Feb 6 '16 at 22:05 add a comment. The lshw stands for List Hardware. It collects the detailed information of the hardware on your. This is our sixth post on getting hardware information. In this post we will see how to get RAM details such as size, speed, make, maximum capacity allowed RAM etc. We already covered some hardware related stuff in this series so far as given below. Get BIOS, Firmware, Hardware And Drivers Details in Linux/Unix What. Slot: L3-Cache size: 6MiB capacity: 6MiB clock: 1GHz (1.0ns) capabilities: pipeline-burst internal write-back unified configuration: level=3.-memory description: System Memory physical id: 32 slot: System board or motherboard size: 32GiB.-bank:0.
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
Entering cat /proc/meminfo in your terminal opens the /proc/meminfo file.
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.
| total | Total installed memory |
| used | Memory currently in use by running processes (used= total – free – buff/cache) |
| free | Unused memory (free= total – used – buff/cache) |
| shared | Memory shared by multiple processes |
| buffers | Memory reserved by the OS to allocate as buffers when process need them |
| cached | Recently used files stored in RAM |
| buff/cache | Buffers + Cache |
| available | Estimation 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.
| Options | Result |
| -b | output in bytes |
| – k | output in kilobytes |
| – m | output in megabytes |
| – g | output in gigabytes |
| – l | detailed low and high memory statistics |
| – o | old format (no -/+buffers/cache line) |
| – t | total for RAM + swap |
| – s | update every [delay] seconds |
| – c | update [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.
- 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.
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:
- The top segment provides summary information and contains graphic meters and text counters.
- The lower section structures the detailed data, per process. This allows you to perform actions on individual processes with ease.
- 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:
- Navigate to Show Applications.
- Enter System Monitor in the search bar and access the application.
- Select the Resources tab.
- 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…
| total | Total installed memory |
| used | Memory currently in use by running processes (used= total – free – buff/cache) |
| free | Unused memory (free= total – used – buff/cache) |
| shared | Memory shared by multiple processes |
| buffers | Memory reserved by the OS to allocate as buffers when process need them |
| cached | Recently used files stored in RAM |
| buff/cache | Buffers + Cache |
| available | Estimation 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.
| Options | Result |
| -b | output in bytes |
| – k | output in kilobytes |
| – m | output in megabytes |
| – g | output in gigabytes |
| – l | detailed low and high memory statistics |
| – o | old format (no -/+buffers/cache line) |
| – t | total for RAM + swap |
| – s | update every [delay] seconds |
| – c | update [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.
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:
- The top segment provides summary information and contains graphic meters and text counters.
- The lower section structures the detailed data, per process. This allows you to perform actions on individual processes with ease.
- 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:
- Navigate to Show Applications.
- Enter System Monitor in the search bar and access the application.
- Select the Resources tab.
- 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…
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…
Finding RAM size details in Linux for a System admin is very easy task. We can use free command to check how much RAM is present in our system. But when you want to find how many RAM/Memory sa lots are present in your system is bit tricky one. One way to do open your system and check what sa lots are there and how much RAM. Instead of doing this as a Hardware engineer we can use a command to check which sa lot is having below details.
- How much RAM
- Speed of the RAM
- Maximum RAM supported by that machine
- RAM location etc.
As you are already aware of dmidecode command to get all the system hardware info. We will use the same command for getting our RAM details.
Linux Get Memory Slot Info
To Find RAM details like maximum RAM, location of RAM etc we can use -t option with dmidecode as shown below
dmidecode -t 16
Output:
# dmidecode 2.11
SMBIOS 2.7 present.
Handle 0x000F, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: No Error
Number Of Devices: 2
If you see the above output we can figure it out how much maximum RAM this machine support, number of RAM devices and location etc.
To get actual RAM details such as how many sa lots, actual RAM present etc, use -t 17 option in dmidecode command
Linux Memory Slot Information Guide
dmidecode -t 17
Output:
# dmidecode 2.11
SMBIOS 2.7 present.
Handle 0x0010, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x000F
Error Information Handle: 0x0011
Total Width: 64 bit's
Data Width: 64 bit's
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: DIMM0
Bank Locator: BANK 0
Type: DDR3
Type Detail: Synchronous
Speed: 1333 MHz
Manufacturer: Kingston
Serial Number: 4B29A74B
Asset Tag: 0123456789
Part Number: 99U5428-046.A00LF
Rank: Unknown
Configured Clock Speed: 1333 MHz
Handle 0x0013, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x000F
Error Information Handle: 0x0014
Total Width: 64 bit's
Data Width: 64 bit's
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 2
Type: DDR3
Type Detail: Synchronous
Speed: 1333 MHz
Manufacturer: Kingston
Serial Number: 4729BF4B
Asset Tag: 0123456789
Part Number: 99U5428-046.A00LF
Rank: Unknown
Configured Clock Speed: 1333 MHz
If we want to see complete RAM details we can use -t memory option to get the details. Note this is a combination of 16 and 17 options
dmidecode -t memory
Linux Memory Usage
Output:
# dmidecode 2.11
SMBIOS 2.7 present.
Handle 0x000F, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: No Error
Number Of Devices: 2
Handle 0x0010, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x000F
Error Information Handle: 0x0011
Total Width: 64 bit's
Data Width: 64 bit's
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: DIMM0
Bank Locator: BANK 0
Type: DDR3
Type Detail: Synchronous
Speed: 1333 MHz
Manufacturer: Kingston
Serial Number: 4B29A74B
Asset Tag: 0123456789
Part Number: 99U5428-046.A00LF
Rank: Unknown
Configured Clock Speed: 1333 MHz
Handle 0x0013, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x000F
Error Information Handle: 0x0014
Total Width: 64 bit's
Data Width: 64 bit's
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 2
Type: DDR3
Type Detail: Synchronous
Speed: 1333 MHz
Manufacturer: Kingston
Serial Number: 4729BF4B
Asset Tag: 0123456789
Part Number: 99U5428-046.A00LF
Rank: Unknown
Configured Clock Speed: 1333 MHz
Some of the valid keywords/types you can use and find different details are as follows.
bios
system
baseboard
chassis
processor
memory
cache
connector
sa lot
We can even use lshw command to get RAM/Memory details as well Cache details such as L1, L2 and L3 levels.
lshw -class memory
*-firmware
description: BIOS
vendor: Hewlett-Packard
physical id: 0
version: F.22
date: 07/27/2011
size: 1MiB
capacity: 2496KiB
capabilities: pci upgrade shadowing cdboot bootselect edd int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
*-memory
description: System Memory
physical id: f
sa lot: System board or motherboard
size: 8GiB
*-bank:0
description: SODIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: 99U5428-046.A00LF
vendor: Kingston
physical id: 0
serial: 4B29A74B
sa lot: DIMM0
size: 4GiB
width: 64 bit's
clock: 1333MHz (0.8ns)
*-bank:1
description: SODIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: 99U5428-046.A00LF
vendor: Kingston
physical id: 1
serial: 4729BF4B
sa lot: DIMM1
size: 4GiB
width: 64 bit's
clock: 1333MHz (0.8ns)
*-cache:0
description: L1 cache
physical id: 1c
sa lot: L1 Cache
size: 32KiB
capacity: 32KiB
capabilities: synchronous internal write-through instruction
*-cache:1
description: L2 cache
physical id: 1d
sa lot: L2 Cache
size: 256KiB
capacity: 256KiB
capabilities: synchronous internal write-through unified
*-cache:2
description: L3 cache
physical id: 1e
sa lot: L3 Cache
size: 3MiB
capacity: 3MiB
capabilities: synchronous internal write-through unified
*-cache
description: L1 cache
physical id: 1b
sa lot: L1 Cache
size: 32KiB
capacity: 32KiB
capabilities: synchronous internal write-through data
Do let us know if there is any way to find RAM sa lot details.
The following two tabs change content below.- Docker: How to copy files to/from docker container - June 30, 2020
- Anisble: ERROR! unexpected parameter type in action: Fix - June 29, 2020
- FREE: JOIN OUR DEVOPS TELEGRAM GROUPS - August 2, 2019
- Review: Whizlabs Practice Tests for AWS Certified Solutions Architect Professional (CSAP) - August 27, 2018
- How to use ohai/chef-shell to get node attributes - July 19, 2018
