Skip to main content

free command and options


Free command is frontend to /proc/meminfo file. It provide more human readable output to show you the total amount of free and used physical and swap memory in the system, as well as the buffers used by the kernel:
$ free -m

vmstat command

===========================================

The vmstat, sar and iostat commands are the collection of package included in sysstat – the system monitoring tools. vmstat - Report virtual memory statistics. It reports information about processes, memory, paging, block IO, traps, disks and cpu activity. The  first report produced gives averages since the last reboot.  Additional reports give information on a sampling period of length delay.
Type the following command:
$vmstat
vmstat.png
FIELD DESCRIPTION FOR VM MODE
  Procs
      r: The number of runnable processes (running or waiting for run time).
      b: The number of processes in uninterruptible sleep.
  Memory
      swpd: the amount of virtual memory used.
      free: the amount of idle memory.
      buff: the amount of memory used as buffers.
      cache: the amount of memory used as cache.
      inact: the amount of inactive memory.  (-a option)
      active: the amount of active memory.  (-a option)
  Swap
      si: Amount of memory swapped in from disk (/s).
      so: Amount of 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: The number of interrupts per second, including the clock.
      cs: The number of context switches per second.
Two important fields are free under memory and si, so under swap column
  1. Free – Amount of free/idle memory spaces.
  2. si – Swapped in every second from disk in Kilo Bytes.
  3. so – Swapped out every second to disk in Kilo Bytes.
OPTIONS
delay  The delay between updates in seconds.  If no delay is specified, only one report is printed with the average values since boot.
count  Number of updates.  In absence of count, when delay is defined, default is infinite.

Execute vmstat ‘X’ seconds and (‘N’ number of times)

$ vmstat 3 5

With this command, vmstat execute every 3 seconds and stop after executing 5 intervals.
Screenshot from 2015-07-22 10:30:41.png

-s, --stats Displays a table of various event counters and memory statistics.  This display does not repeat.
$ vmstat -s
Screenshot from 2015-07-22 10:32:12.png
-S, --unit character Switches outputs between 1000 (k), 1024 (K), 1000000 (m), or 1048576 (M) bytes.  Note this does not change the swap (si/so) or block
             (bi/bo) fields.
The vmstat displays in Megabytes with parameters -S and m. By default vmstat displays statistics in kilobytes.
$ vmstat -S m
Screenshot from 2015-07-22 10:36:29.png
    -d, --disk Report disk statistics
        $ vmstat -d
        Screenshot from 2015-07-22 10:42:07.png
Labels:

Popular posts from this blog

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .     How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Updated: 2026 (Original article published August 02, 2011) Email confirmation is an integral part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding emails. Sooner or later, every automation engineer faces the same challenge: How do we verify an email confirmation link inside a Selenium test without making the test slow and flaky? Many beginners try to automate Gmail UI using Selenium. That approach is fragile, slow, and tightly coupled to a third-party UI that changes frequently. A cleaner approach is this: Use Selenium for browser automation. Use JavaMail (IMAP) to read the email directly. Extract the confirmation link. Continue the test using Selenium. This guide shows a modern, production-ready approach using Selenium 4 and JavaMail . Why Not Auto...
13 comments
Read more

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -
8 comments
Read more

Capture network traffic using WebDriver

We often come across testing requirements when we need to analyze the network traffic to find - HTTP status of page Analyze header information to find if right information is passed Validating parameters related to ajax requests etc Selenium 1 has had a way to capture n/w traffic but the feature does not always work as expected. At times Selenium 1 does not capture all n/w traffic, And given that Selenium 1 APIs are almost dead it is
4 comments
Read more