aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSeongJae Park <sj38.park@gmail.com>2024-03-31 10:48:17 -0700
committerSeongJae Park <sj38.park@gmail.com>2024-03-31 10:48:17 -0700
commit8589420066972f089089511150c7a2e4dbbdc784 (patch)
treee1751ea6980782c35c9900842340a5c19464168d
parent4c9b5cdea58ed4e36fa7bb991a97557582c1109d (diff)
downloaddamo-8589420066972f089089511150c7a2e4dbbdc784.tar.gz
USAGE: Document --footprint option of 'damo record'
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
-rw-r--r--USAGE.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/USAGE.md b/USAGE.md
index 6a34abf0..a1a575ea 100644
--- a/USAGE.md
+++ b/USAGE.md
@@ -454,6 +454,25 @@ Because the profile information record file is simply `perf record` output,
users can further analyze the profile information using `perf` or any `perf
record` output compatible tools.
+### Recording Memory Footprints
+
+Note: This is an experimental feature at the moment. Some changes could be
+made, or the support can be dropped in future.
+
+Users can record memory usage information of the record target processes
+together with the access pattern by adding `--footprint` command line option to
+the `damo record` command. Internally, it parses `/proc/<pid>/statm` files for
+the monitoring target processes, and save the results as a json file of the
+name same to the access pattern record file (specified by `--out` option of
+`damo record`) except having `.mem_footprint` suffix. Hence,
+`damon.data.mem_footprint` is the default name of the profile information.
+
+Users could use the files for vaious purpose. For an example, users could find
+when how much memory is allocated by the process and really accessed, by
+comparing the recorded residential set size and DAMON-based working set size.
+Support of visualization of such information is one of the future works at the
+moment.
+
`damo report` (Visualizing Recorded Data Access Pattern)
--------------------------------------------------------