From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 0/4] perf annotate: Improve memory usage for symbol histogram
Date: Mon, 4 Mar 2024 14:53:59 -0800 [thread overview]
Message-ID: <CAM9d7cggEAm3qyaBYVhpAXbGJ8LjJjK67WPds9dAFd_F5NJbhA@mail.gmail.com> (raw)
In-Reply-To: <CAM9d7chEoab71v8=th7NAWcsPPZV+oGiJPGfiCcjdS3L+u13dA@mail.gmail.com>
On Mon, Mar 4, 2024 at 8:36 AM Namhyung Kim <namhyung@kernel.org> wrote:
>
> Hi Arnaldo,
>
> On Mon, Mar 4, 2024 at 5:58 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > On Tue, Feb 27, 2024 at 04:52:26PM -0800, Namhyung Kim wrote:
> > > This is another series of memory optimization in perf annotate.
> >
> > > When perf annotate (or perf report/top with TUI) processes samples, it
> > > needs to save the sample period (overhead) at instruction level. For
> > > now, it allocates an array to do that for the whole symbol when it
> > > hits any new symbol. This comes with a lot of waste since samples can
> > > be very few and instructions span to multiple bytes.
> >
> > > For example, when a sample hits symbol 'foo' that has size of 100 and
> > > that's the only sample falls into the symbol. Then it needs to
> > > allocate a symbol histogram (sym_hist) and the its size would be
> >
> > > 16 (header) + 16 (sym_hist_entry) * 100 (symbol_size) = 1616
> >
> > > But actually it just needs 32 (header + sym_hist_entry) bytes. Things
> > > get worse if the symbol size is bigger (and it doesn't have many
> > > samples in different places). Also note that it needs separate
> > > histogram for each event.
> >
> > > Let's split the sym_hist_entry and have it in a hash table so that it
> > > can allocate only necessary entries.
> >
> > > No functional change intended.
> >
> > I tried this before/after this series:
> >
> > $ time perf annotate --stdio2 -i perf.data.annotate
> >
> > For:
> >
> > perf record -e '{cycles,instructions,cache-misses}' make -k CORESIGHT=1 O=/tmp/build/$(basename $PWD)/ -C tools/perf install-bin
> >
> > And found these odd cases:
> >
> > $ diff -u before after
> > --- before 2024-02-28 15:38:25.086062812 -0300
> > +++ after 2024-02-29 14:12:05.606652725 -0300
> > @@ -2450826,7 +2450826,7 @@
> > ↓ je 1c62
> > → call operator delete(void*)@plt
> > { return _M_dataplus._M_p; }
> > - 1c62: mov 0x13c0(%rsp),%rdi
> > + 0.00 0.00 100.00 1c62: mov 0x13c0(%rsp),%rdi
> > if (_M_data() == _M_local_data())
> > lea 0x13d0(%rsp),%rax
> > cmp %rax,%rdi
> > @@ -2470648,7 +2470648,7 @@
> > mov %rbx,%rdi
> > → call operator delete(void*)@plt
> > using reference = T &;
> > - 0.00 0.00 100.00 11c65: mov 0x8(%r12),%rax
> > + 11c65: mov 0x8(%r12),%rax
> > size_t size() const { return Size; }
> > mov 0x10(%r12),%ecx
> > mov %rax,%rbp
> > $
> >
> >
> > This is a large function:
>
> Thanks for the test! I think it missed the cast to 64-bit somewhere.
> I'll check and send v2 soon.
Yep, the offset variable in __symbol__inc_addr_samples()
should be u64.
Thanks,
Namhyung
prev parent reply other threads:[~2024-03-04 22:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 0:52 [PATCH 0/4] perf annotate: Improve memory usage for symbol histogram Namhyung Kim
2024-02-28 0:52 ` [PATCH 1/4] perf annotate: Add a hashmap " Namhyung Kim
2024-02-28 1:19 ` Ian Rogers
2024-02-28 5:21 ` Namhyung Kim
2024-02-28 0:52 ` [PATCH 2/4] perf annotate: Calculate instruction overhead using hashmap Namhyung Kim
2024-02-28 5:43 ` Namhyung Kim
2024-02-28 0:52 ` [PATCH 3/4] perf annotate: Remove sym_hist.addr[] array Namhyung Kim
2024-02-28 0:52 ` [PATCH 4/4] perf annotate: Add comments in the data structures Namhyung Kim
2024-02-28 1:20 ` [PATCH 0/4] perf annotate: Improve memory usage for symbol histogram Ian Rogers
2024-03-04 13:58 ` Arnaldo Carvalho de Melo
2024-03-04 16:36 ` Namhyung Kim
2024-03-04 22:53 ` Namhyung Kim [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=CAM9d7cggEAm3qyaBYVhpAXbGJ8LjJjK67WPds9dAFd_F5NJbhA@mail.gmail.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).