1cachetop(8) System Manager's Manual cachetop(8)
2
3
4
6 cachetop - Statistics for linux page cache hit/miss ratios per pro‐
7 cesses. Uses Linux eBPF/bcc.
8
10 cachetop [interval]
11
13 This traces four kernel functions and prints per-processes summaries
14 every interval seconds. This can be useful for processes workload char‐
15 acterization, and looking for patterns in operation usage over time. It
16 provides a top-like interface which by default sorts by HITS in ascend‐
17 ing order.
18
19 This works by tracing kernel page cache functions using dynamic trac‐
20 ing, and will need updating to match any changes to these functions.
21 Edit the script to customize which functions are traced.
22
23 Since this uses BPF, only the root user can use this tool.
24
26 The following keybindings can be used to control the output of
27 cachetop.
28
29 < Use the previous column for sorting.
30
31 > Use the next column for sorting.
32
33 r Toggle sorting order (default ascending).
34
35 q Quit cachetop.
36
38 CONFIG_BPF and bcc.
39
41 Update summaries every five second:
42 # cachetop
43
44 Print summaries each second:
45 # cachetop 1
46
48 PID Process ID of the process causing the cache activity.
49
50 UID User ID of the process causing the cache activity.
51
52 HITS Number of page cache hits.
53
54 MISSES Number of page cache misses.
55
56 DIRTIES
57 Number of dirty pages added to the page cache.
58
59 READ_HIT%
60 Read hit percent of page cache usage.
61
62 WRITE_HIT%
63 Write hit percent of page cache usage.
64
65 BUFFERS_MB
66 Buffers size taken from /proc/meminfo.
67
68 CACHED_MB
69 Cached amount of data in current page cache taken from
70 /proc/meminfo.
71
73 This traces various kernel page cache functions and maintains in-kernel
74 counts, which are asynchronously copied to user-space. While the rate
75 of operations can be very high (>1G/sec) we can have up to 34% over‐
76 head, this is still a relatively efficient way to trace these events,
77 and so the overhead is expected to be small for normal workloads. Mea‐
78 sure in a test environment.
79
81 This is from bcc.
82
83 https://github.com/iovisor/bcc
84
85 Also look in the bcc distribution for a companion _examples.txt file
86 containing example usage, output, and commentary for this tool.
87
89 Linux
90
92 Unstable - in development.
93
95 Emmanuel Bretelle
96
98 cachestat (8)
99
100
101
102USER COMMANDS 2016-01-30 cachetop(8)