From 5290e2abccd68fc95efd109f1fa088ed84fb6c34 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0pa=C4=8Dek?= Date: Thu, 14 Sep 2023 14:54:23 +0000 Subject: [PATCH] Update BIND 9 Memory Explained: mention why top is rubbish --- BIND-9-Memory-Explained.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/BIND-9-Memory-Explained.md b/BIND-9-Memory-Explained.md index 438dbd6..c39b48f 100644 --- a/BIND-9-Memory-Explained.md +++ b/BIND-9-Memory-Explained.md @@ -98,7 +98,9 @@ MALLOCED: 13.3MiB == 13.3MiB The rule of thumb is > Don't use the `top` command -There are better tools that are less misleading. There are two tools the are easily available on modern Linux systems - `pmap` and `smem`. +There are better tools that are less misleading. Most importantly the VIRT value reported by `top` (and VSZ value reported by `ps`) are meaningless. + +There are two better tools the are easily available on modern Linux systems - `pmap` and `smem`. #### pmap