From: Jiri Olsa <jolsa@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Michael Petlan <mpetlan@redhat.com>,
Ian Rogers <irogers@google.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [RFC] perf record: Disable debuginfod by default
Date: Sun, 19 Dec 2021 14:04:45 +0100 [thread overview]
Message-ID: <Yb8t7R577H3DiJGz@krava> (raw)
In-Reply-To: <20211210165010.GA30236@redhat.com>
On Fri, Dec 10, 2021 at 11:50:10AM -0500, Frank Ch. Eigler wrote:
> Hi -
>
> On Fri, Dec 10, 2021 at 01:23:32PM +0100, Jiri Olsa wrote:
> > [...]
> > at the end of the perf record we populate buildid cache
> > with profiled binaries for the current perf.data
> >
> > **IF** there's DEBUGINFOD_URLS defined, that code will
> > also ask debuginfod for binaries it could not find on
> > the system
>
> Consider doing this only at the end of the run, and in the background,
> just as a prefetch for the perf report step? The main downside there
> could be if one runs many perf record jobs in close proximity,
> overlapping larger prefetch download tasks. That might waste some
> network traffic.
right, IMO it's too much for default behaviour but I think could
do this under new (config) option, if there's a need for that
thanks,
jirka
next prev parent reply other threads:[~2021-12-19 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 20:04 [RFC] perf record: Disable debuginfod by default Jiri Olsa
2021-12-09 23:39 ` Namhyung Kim
2021-12-10 12:23 ` Jiri Olsa
2021-12-10 16:50 ` Frank Ch. Eigler
2021-12-19 13:04 ` Jiri Olsa [this message]
2021-12-10 18:41 ` Namhyung Kim
2021-12-11 19:57 ` Jiri Olsa
2021-12-10 8:04 ` Peter Zijlstra
2021-12-10 12:24 ` Jiri Olsa
2021-12-10 13:33 ` Arnaldo Carvalho de Melo
2021-12-19 13:06 ` Jiri Olsa
2022-01-15 20:22 ` Arnaldo Carvalho de Melo
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=Yb8t7R577H3DiJGz@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=fche@redhat.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.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).