This page describes additional documentation,
links to related sites, examples of scripts, etcetera.
- Case study with atop: memory leakage
This article describes
the analysis of a system suffering from a process with a memory
leakage. It also describes a way to control such misbehaving process
(i.e. avoid that the entire system suffers) for the time that the
problem has not been solved in the applications' code.
- Manual pages
Online manual pages of
- Linux performance analysis and tuning
This master class
(four days) provides knowledge about the way that the Linux kernel distrbutes
the capacity of
the performance-critical hardware resources (CPU, memory, disk, network).
With this information in mind, the counters of
atop/atopsar and many other tools are discussed. Furthermore, methods are
offered to improve the performance of your system, a.o. by using cgroups
to subdivide the bandwidth of your hardware resources in a better way.
The master class is offered in
English and Dutch.
The tar archive
atopscripts (version 1.1) contains scripts
to be used to process output of atop/atopsar:
Script that displays an overview of the virtual memory growth per process
during the last 14 days (the daily memory size of processes at 5:00 PM is taken).
Processes that were only present for 1 day and processes that did not grow
are ignored. The list shows per process the PID and process name,
how many days the process has lived (max. 14 days), the total growth of
the virtual memory consumption during that number of days, and the growth
per day (in MiB).
Notice that not every process that grows is a process suffering from a memory leak!
Mainly processes that have a daily growth are suspects.
Version 1.1 contains some bugfixes (explicit use of bash and proper use of awk sub()).
Credits: Gerrit Smit