linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Raghavendra K T <raghavendra.kt@amd.com>
To: David Rientjes <rientjes@google.com>,
	Michal Hocko <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>,
	Balbir Singh <bsingharora@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-mm@kvack.org, "Rao, Bharata Bhasker" <bharata@amd.com>,
	Shivank Garg <shivankg@amd.com>,
	ayush.jain3@amd.com, "Shukla, Santosh" <Santosh.Shukla@amd.com>,
	"Grimm, Jon" <jon.grimm@amd.com>
Subject: Re: Tools for explaining memory mappings/usage/pressure
Date: Mon, 30 Dec 2024 13:45:01 +0530	[thread overview]
Message-ID: <1a2bc48c-470d-4a70-a502-2dbcaddb72d1@amd.com> (raw)
In-Reply-To: <29c27dab-a590-5df2-c840-279bf9dff090@google.com>

On 7/7/2024 2:25 AM, David Rientjes wrote:
> Hi all,
> 
> I'm trying to crowdsource information on open source tools that can be
> used directly by customers to explain memory mappings, usage, pressure,
> etc.
> 
> We encounter both internal and external users that are looking for this
> insight and it often requires significant engineering time to collect data
> to make any conclusions.

Hello David,

Link: https://github.com/AMDESE/workload-insight-tool

sorry for replying late (as we took few months to make the
tool "opensource").

Not sure whether it exactly fits the requirement but the tools has been
very helpful for us (developers) to "visualize" the system behavior
(that is exported via procfs /sysfs interface) and initial analysis.

Deploying is easy since it is provided as a python package.

Typical usage:
1. collect the behavior of workload using
$syswit collect
e.g.,
$syswit collect -c "<PWD>/syswit/collector_configs/numa_cxl.yaml"  -C -T 
-m 1 -w "<workload>"

collected information is stored in Json format and it can be compared/
visualized further with
$syswit analyze (behavior of single workload)
OR
$syswit compare (comparing the result with multiple workload run
(e.g., before / after the patch).

Still a Long way to go.. But hope it is useful.

[Idea about the tool was seeded by Bharata, Bharata/Me helped in some of
the design and optimization and Ayush is the sole developer and many
inside AMD helped in reviewing/improving (Shivank,....)].

USP:
1. we can tune the information to collect.
2. It can run for longer time and store the data that can be analyzed/
visualized offline  for anomaly.

(Thinking whether I should also post as a main thread in linux-mm
for greater awareness)

Thanks and Regards
- Raghu


      parent reply	other threads:[~2024-12-30  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06 20:55 David Rientjes
2024-07-07 15:44 ` SeongJae Park
2024-07-08 13:50 ` Dan Schatzberg
2024-07-21 23:05   ` David Rientjes
2024-07-22 22:15     ` Dan Schatzberg
2024-07-22  9:05 ` Vlastimil Babka (SUSE)
2024-07-22 21:57   ` David Rientjes
2024-12-30  8:15 ` Raghavendra K T [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1a2bc48c-470d-4a70-a502-2dbcaddb72d1@amd.com \
    --to=raghavendra.kt@amd.com \
    --cc=Santosh.Shukla@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=ayush.jain3@amd.com \
    --cc=bharata@amd.com \
    --cc=bsingharora@gmail.com \
    --cc=jon.grimm@amd.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=shivankg@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox