vmstat -- virtual memory statistics

The first tool to use for locating performance bottlenecks is the vmstat command. It provides compact table-based snapshot of  various system resources utilization. vmstat does not count itself as a running process.  The following metrics might help to determine the  overloaded system are

• r: The number of processes in the run queue waiting for CPU. Value  usually should not exceed  number of processors (or cores). Double digit reading often signals that there is a bottleneck somewhere in the system. In a response sensitive servers (Web servers, terminal servers) this parameter should be close to zero. In a nutshell, non-zero values represent the size of  CPU queue -- tasks waiting on busy CPU(s) or tasks waiting because of data-serialization issues. In you encounter number higher then the number of CPUs on the system you should probably have a look on the system and see what process is taking most of the cpu (use the top command).
• b: The number of processes/threads sleeping (blocked processes usually waiting for IO). A sleeping process is created when a program makes a request that can't be immediately fulfilled. High number might suggest I/O bottleneck.
• so: Amount of memory swapped to disk (/s). Most production systems should not swap memory to disk during normal operation. Non-zero value usually means that the amount of physical memory is insufficient for optimal operations of the system with a given load.
• wa: Time spent waiting for IO.  Double digits value suggests I/O bottleneck.

For analysis of long intervals output from sar might be a good alternative. In both cases one can pipe output into Perl script to produce alerts. For example if a single cpu dual core Linux 2.6 server demonstrated strange behavior with uptime averages above 12 (case that happened to the author). In this case to lessen the amount of collected information you can use threshold 4 for "r"; exceeding this threshold triggers writing vmstat or sar information to log and/or and piping it into Perl script for detailed analysis.

 If the vmstat command is used without any options, it reports the current set of statistics and exits. If a single numeric argument T is supplied it is assumed to be an interval (in seconds) between iterations of the report and vmstat runs in a loop outputting the statistics each T seconds. Optionally the second numerical parameter can be specified which provides the number of iterations of the time loop. For example vmstat 2 10 means output statistics each 2 sec and make 10 iterations before existing.

vmstat reports virtual memory statistics regarding kernel thread, virtual memory, disk, trap, and CPU activity.  Traditionally those parts of the table have headers

• procs
  • r: The number of processes waiting for run time.
  • b: The number of processes sleeping (usually waiting for IO).
• memory (self-explainable columns swpd, free, buff and cache):
  • swpd Virtual memory used, in kilobytes.
  • free Idle memory, in kilobytes.
  • buff Memory used as buffers, in kilobytes.
  • cache Cache memory, in kilobytes.
  • inactive Inactive memory, in kilobytes, displayed with -a.
  • active Active memory, in kilobytes; displayed with -a.
• swap (columns si and so  -- Memory swapped in/out from disk each second, in kilobytes.)  
• 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.
•  cpu
  • us: Time spent running non-kernel code. (user time, including nice time)
  • sy: Time spent running kernel code. (system time)
  • id: Time spent idle.
  • wa Percentage of CPU time spent waiting for I/O.

On MP (multi-processor) systems, vmstat averages the number of CPUs into the output. For per-processor statistics, see mpstat(1M). vmstat only supports statistics for certain devices. For more general system statistics, you can also use e sar and  iostat. command.

Without options, vmstat displays a one-line summary of the virtual memory activity since the system was booted.

Solaris vmstat

vmstat [-cipqsS] [disks] [interval[count]]

The output from the Solaris vmstat command without options is:

 procs     memory            page            disk          faults      cpu
 r b w   swap  free  re  mf pi po fr de sr f0 s1 s2 s3   in   sy   cs us sy id
 0 0 0  15020  4304   9  58 198 228 220 0 3 0 16  1  1   86 1173   46 24 30 46

procs  reports on process states. r  is the number of processes in the run queue. b  is the number of processes blocked and waiting for resources such as disk or terminal input. w  is the number of runnable processes, or processes swapped but in a sleep state of less than twenty seconds.

Under the memory  heading statistics are given on the usage of real and virtual memory. swap  reports the available swap space in Kilobytes. free  gives the size of the free list.

Under the page heading, page faults and page activity is reported in units per second. Page faulting occurs when the system attempts to access an unmapped page. Statistics are reported as follows:

• re  The number of pages reclaimed.
• mf  The number of major and minor faults.
• pi  The kilobytes paged in.
• po  The kilobytes paged out.
• fr  The kilobytes freed.
• de  The amount of anticipated memory needed by processes that have recently swapped in.
• sr  The pages scanned by the page daemon.

disk  lists the number of disk operations per second and can show data for up to four disks at a time. Which disks to report can be passed to the vmstat command.

faults  reports the trap or interrupt rate per second. in  is the number if device interrupts per second. sy  is the number of system calls and cs  is the CPU context switch rate.

The last group of statistics pertain to CPU usage. The amount of time spent in user mode, kernel mode and idle are reported.

vmstat can also report on swapping and cache flushing. The -S adds two fields to the beginning of the paging statistics. These are si, which lists the number of pages swapped in per second, and so, which gives the number of entire processes swapped out.

vmstat -c displays cache flushing statistics for a virtual cache. The number of cache flushes since the last reboot are listed. The output of this command looks like:

 flush statistics: (totals)
     usr     ctx     rgn     seg     pag     par
       0       0       0       0       0       0

• usr  User
• ctx  Context
• rgn  Region
• seg  Segment
• pag  Page
• par  Partial-page

vmstat -i displays the number of interrupts per device. The output looks like:

interrupt         total     rate
--------------------------------
clock          98080370      100
fdc0                 14        0
--------------------------------
Total          98080384      100

NEWS CONTENTS

• 190321 : Examining vmstat AIX IBM Systems Magazine ( Examining vmstat AIX IBM Systems Magazine, )
• 190321 : Monitoring Virtual Memory with vmstat ( Monitoring Virtual Memory with vmstat, )

Old News ;-)

Examining vmstat AIX IBM Systems Magazine

My favorite coarse-grained tool for monitoring servers is definitely the venerable vmstat. After the eyes have been trained to interpret the data, it's amazing what can be gleaned from this tool.

The Basics
In AIX* 5.1, vmstat has the following syntax options:

vmstat [ -f ] [ -i ] [ -s ] [ -I ] [ -t ]
[ PhysicalVolume ... ] [ Interval [Count ] ]

From the AIX 5.1 "man" pages, the vmstat command reports statistics about kernel threads, virtual memory, disks, traps and CPU activity. These system-wide (among all processors) statistics are calculated as averages for values expressed as percentages and as sums otherwise. If the vmstat command is invoked without flags, the report contains a summary of activity since system startup. The interval parameter specifies the amount of time between each report in seconds. The first report contains statistics for the time since startup. Subsequent reports contain statistics collected during the interval since the previous report.

Figure 1(see below) shows data collected on an AIX 5.1 server using the command: $ vmstat -It 15 16 (boot line has been removed).

The first three columns in Figure 1 list information about threads. "r" reports the average total number of kernel, kernel-managed and user threads in the global run queue (per second). In a nutshell, non-zero values represent a CPU queue--tasks waiting on busy CPU(s) or tasks waiting because of data-serialization issues.

Conceptually, a thread is a distinct sequence of execution steps performed within a process. Each thread has its own stack, register set, program counter, thread-specific data, thread-local variables, thread-specific signal mask and state information. However, all such threads share the same address space (program text, data and heap), open files pointers, user credentials, management data and I/O with the other threads in the same process.

In AIX, the kernel allows many threads to run at the same time, but there can only be one thread actually executing on each CPU. (Note: Starting with the POWER5* processor, a hardware configuration called simultaneous multithreading allows two threads to be running in each processor core). Every process has at least one thread; some processes have many. The scheduler and dispatcher only work with threads. Threads can be viewed with the ps -emo THREAD command.

AIX has three types of threads: kernel, kernel-managed and user. Kernel threads aren't associated with a user process, and therefore have no user context. They run in kernel mode and have their own kernel stack. These threads are also inexpensive to create and manage, so they're typically used to perform a specific function like asynchronous I/O.

Monitoring Virtual Memory with vmstat

Linux novices often find virtual memory mysterious, but with a grasp of the fundamental concepts, it's easy to understand. With this knowledge, you can monitor your system's memory utilization using vmstat and detect problems that can adversely affect system performance.

How Virtual Memory Works

Physical memory-the actual RAM installed-is a finite resource on any system. The Linux memory handler manages the allocation of that limited resource by freeing portions of physical memory when possible.

All processes use memory, of course, but each process doesn't need all its allocated memory all the time. Taking advantage of this fact, the kernel frees up physical memory by writing some or all of a process' memory to disk until it's needed again.

The kernel uses paging and swapping to perform this memory management. Paging refers to writing portions, termed pages, of a process' memory to disk. Swapping, strictly speaking, refers to writing the entire process, not just part, to disk. In Linux, true swapping is exceedingly rare, but the terms paging and swapping often are used interchangeably.

When pages are written to disk, the event is called a page-out, and when pages are returned to physical memory, the event is called a page-in. A page fault occurs when the kernel needs a page, finds it doesn't exist in physical memory because it has been paged-out, and re-reads it in from disk.

Page-ins are common, normal and are not a cause for concern. For example, when an application first starts up, its executable image and data are paged-in. This is normal behavior.

Page-outs, however, can be a sign of trouble. When the kernel detects that memory is running low, it attempts to free up memory by paging out. Though this may happen briefly from time to time, if page-outs are plentiful and constant, the kernel can reach a point where it's actually spending more time managing paging activity than running the applications, and system performance suffers. This woeful state is referred to as thrashing.

Using swap space is not inherently bad. Rather, it's intense paging activity that's problematic. For instance, if your most-memory-intensive application is idle, it's fine for portions of it to be set aside when another large job is active. Memory pages belonging to an idle application are better set aside so the kernel can use physical memory for disk buffering.

Using vmstat

vmstat, as its name suggests, reports virtual memory statistics. It shows how much virtual memory there is, how much is free and paging activity. Most important, you can observe page-ins and page-outs as they happen. This is extremely useful.

To monitor the virtual memory activity on your system, it's best to use vmstat with a delay. A delay is the number of seconds between updates. If you don't supply a delay, vmstat reports the averages since the last boot and quit. Five seconds is the recommended delay interval.

To run vmstat with a five-second delay, type:

vmstat 5

You also can specify a count, which indicates how many updates you want to see before vmstat quits. If you don't specify a count, the count defaults to infinity, but you can stop output with Ctrl-C.

To run vmstat with ten updates, five seconds apart, type:

vmstat 5 10

Here's an example of a system free of paging activity:

  procs                     memory    swap        io     system cpu
r  b  w   swpd   free  buff  cache  si so   bi  bo   in    cs us sy  id
0  0  0  29232 116972  4524 244900   0  0    0   0    0     0 0   0   0
0  0  0  29232 116972  4524 244900   0  0    0   0 2560     6 0   1  99
0  0  0  29232 116972  4524 244900   0  0    0   0 2574    10 0   2  98

All fields are explained in the vmstat man page, but the most important columns for this article are free, si and so. The free column shows the amount of free memory, si shows page-ins and so shows page-outs. In this example, the so column is zero consistently, indicating there are no page-outs.

The abbreviations so and si are used instead of the more accurate po and pi for historical reasons.

Here's an example of a system with paging activity:

  procs          memory             swap      io       system  --- cpu ---
r  b  w   swpd   free  buff cache  si  so   bi   bo   in    cs us  sy  id
. . .
1  0  0  13344   1444  1308 19692   0 168  129   42 1505   713 20  11  69
1  0  0  13856   1640  1308 18524  64 516  379  129 4341   646 24  34  42
3  0  0  13856   1084  1308 18316  56  64   14    0  320  1022 84   9   8

Notice the nonzero so values indicating there is not enough physical memory and the kernel is paging out. You can use top and ps to identify the processes that are using the most memory.

You also can use top to show memory and swap statistics. Here is an example of the uppermost portion of a typical top report:

14:23:19 up 348 days,  3:02,  1 user,  load average: 0.00, 0.00, 0.00
55 processes: 54 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:   0.0% user,   2.4% system,   0.0% nice,  97.6% idle
Mem:    481076K total,   367508K used,   113568K free,     4712K buffers
Swap:  1004052K total,    29852K used,   974200K free,   244396K cached

Recommended Links

• vmstat - Wikipedia, the free encyclopedia
• Examining vmstat AIX IBM Systems Magazine
• Monitoring Virtual Memory with vmstat
• Memory usage determination with the vmstat command (AIX)
• Solaris Performance Monitoring - iostat , vmstat , netstat
• AIX man page
• RedHat provides more details on this here, here and here to explain vmstat output. And a related post on tuning Oracle on RedHat Linux is here.

Linux

vmstat reports information about processes, memory, paging, block IO, traps, and cpu activity.

The first report produced gives averages since the last reboot. Additional reports give information on a sampling period of length delay. The process and memory reports are instantaneous in either case.

Options

• -a displays active/inactive memory, given a 2.5.41 kernel or better.
• -f displays the number of forks since boot. This includes the fork, vfork, and clone system calls, and is equivalent to the total number of tasks created. Each process is represented by one or more tasks, depending on thread usage. This display does not repeat.
• -m displays slabinfo.
• -n causes the header to be displayed only once rather than periodically.
• -s displays a table of various event counters and memory statistics. This display does not repeat.
• delay is the delay between updates in seconds. If no delay is specified, only one report is printed with the average values since boot.
• count is the number of updates. If no count is specified and delay is defined, count defaults to infinity.
• -d reports disk statistics (2.5.70 or above required)
• -p followed by some partition name for detailed statistics (2.5.70 or above required)
• -S followed by k or K or m or M switches outputs between 1000, 1024, 1000000, or 1048576 bytes
• -V switch results in displaying version information.

Field Description For Vm Mode

Procs

• r: The number of processes 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.

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.

  Prior to Linux 2.5.41, this includes IO-wait time. wa: Time spent waiting for IO. Prior to Linux 2.5.41, included in idle. st: Time stolen from a virtual machine. Prior to Linux 2.6.11, unknown.

Field Description For Disk Mode

Reads

total: Total reads completed successfully merged: grouped reads (resulting in one I/O) sectors: Sectors read successfully ms: milliseconds spent reading

Writes

total: Total writes completed successfully merged: grouped writes (resulting in one I/O) sectors: Sectors written successfully ms: milliseconds spent writing

IO

cur: I/O in progress
s: seconds spent for I/O

Field Description For Disk Partition Mode

reads: Total number of reads issued to this partition read sectors: Total read sectors for partition writes : Total number of writes issued to this partition requested writes: Total number of write requests made for partition

Field Description For Slab Mode

cache: Cache name num: Number of currently active objects total: Total number of available objects size: Size of each object pages: Number of pages with at least one active object totpages: Total number of allocated pages pslab: Number of pages per slab

Notes

vmstat does not require special permissions.

These reports are intended to help identify system bottlenecks. Linux vmstat does not count itself as a running process.

All linux blocks are currently 1024 bytes. Old kernels may report blocks as 512 bytes, 2048 bytes, or 4096 bytes.

Since procps 3.1.9, vmstat lets you choose units (k, K, m, M) default is K (1024 bytes) in the default mode

vmstat uses slabinfo 1.1 FIXME

Files

/proc/meminfo
/proc/stat
/proc/*/stat

See Also

iostat(1), sar(1), mpstat(1), ps(1), top(1), free(1)

Solaris 10

See System Administration Guide: Advanced Administration for device naming conventions for disks.

OPTIONS

The following options are supported:

-c

Report cache flushing statistics. This option is obsolete, and no longer meaningful. This option might be removed in a future version of Solaris.

-i

Report the number of interrupts per device. count and interval does not apply to the -i option.

-p

Report paging activity in details. This option will display the following, respectively:

epi

Executable page-ins.

epo

Executable page-outs.

epf

Executable page-frees.

api

Anonymous page-ins.

apo

Anonymous page-outs.

apf

Anonymous page-frees.

fpi

File system page-ins.

fpo

File system page-outs.

fpf

File system page-frees.

When executed in a zone and if the pools facility is active, all of the above only report actitivity on the processors in the processor set of the zone's pool.

-q

Suppress messages related to state changes.

-s

Display the total number of various system events since boot. count and interval does not apply to the -s option.

-S

Report on swapping rather than paging activity. This option will change two fields in vmstat's ``paging'' display: rather than the ``re'' and ``mf'' fields, vmstat will report ``si'' (swap-ins) and ``so'' (swap-outs).

OPERANDS

The following operands are supported:

count

Specifies the number of times that the statistics are repeated. count does not apply to the -i and -s options.

disks

Specifies which disks are to be given priority in the output (only four disks fit on a line). Common disk names are id, sd, xd, or xy, followed by a number (for example, sd2, xd0, and so forth).

interval

Specifies the last number of seconds over which vmstat summarizes activity. This number of seconds repeats forever. interval does not apply to the -i and -s options.

EXAMPLES

---

Example 1 Using vmstat

The following command displays a summary of what the system is doing every five seconds.

example% vmstat 5
kthr   memory          page             disk      faults        cpu
r b w swap  free re mf pi p fr de sr s0 s1 s2 s3  in  sy  cs us sy id
0 0 0 11456 4120 1  41 19 1  3  0  2  0  4  0  0  48 112 130  4 14 82
0 0 1 10132 4280 0   4 44 0  0  0  0  0 23  0  0 211 230 144  3 35 62
0 0 1 10132 4616 0   0 20 0  0  0  0  0 19  0  0 150 172 146  3 33 64
0 0 1 10132 5292 0   0  9 0  0  0  0  0 21  0  0 165 105 130  1 21 78
1 1 1 10132 5496 0   0  5 0  0  0  0  0 23  0  0 183  92 134  1 20 79
1 0 1 10132 5564 0   0 25 0  0  0  0  0 18  0  0 131 231 116  4 34 62
1 0 1 10124 5412 0   0 37 0  0  0  0  0 22  0  0 166 179 118  1 33 67
1 0 1 10124 5236 0   0 24 0  0  0  0  0 14  0  0 109 243 113  4 56 39
‸Cexample%

The fields of vmstat's display are

kthr

Report the number of kernel threads in each of the three following states:


r

the number of kernel threads in run queue

b

the number of blocked kernel threads that are waiting for resources I/O, paging, and so forth

w

the number of swapped out lightweight processes (LWPs) that are waiting for processing resources to finish.

memory

Report on usage of virtual and real memory.

swap

available swap space (Kbytes)

free

size of the free list (Kbytes)

page

Report information about page faults and paging activity. The information on each of the following activities is given in units per second.

re

page reclaims - but see the -S option for how this field is modified.

mf

minor faults - but see the -S option for how this field is modified.

pi

kilobytes paged in

po

kilobytes paged out

fr

kilobytes freed

de

anticipated short-term memory shortfall (Kbytes)

sr

pages scanned by clock algorithm

When executed in a zone and if the pools facility is active, all of the above (except for "de") only report activity on the processors in the processor set of the zone's pool.

disk

Report the number of disk operations per second. There are slots for up to four disks, labeled with a single letter and number. The letter indicates the type of disk (s = SCSI, i = IPI, and so forth); the number is the logical unit number.

faults

Report the trap/interrupt rates (per second).

in

interrupts

sy

system calls

cs

CPU context switches

When executed in a zone and if the pools facility is active, all of the above only report actitivity on the processors in the processor set of the zone's pool.

cpu

Give a breakdown of percentage usage of CPU time. On MP systems, this is an average across all processors.

us

user time

sy

system time

id

idle time

When executed in a zone and if the pools facility is active, all of the above only report actitivity on the processors in the processor set of the zone's pool.

---

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWcsu
Interface Stability	See below.

Invocation is evolving. Human readable output is unstable.

SEE ALSO

sar(1), iostat(1M), mpstat(1M), sar(1M), attributes(5)

System Administration Guide: Basic Administration

System Administration Guide: Advanced Administration

NOTES

The sum of CPU utilization might vary slightly from 100 because of rounding errors in the production of a percentage figure.

The -c option (Report cache flushing statistics) is not supported in this release.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019