[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211210165010.GA30236@redhat.com>
Date: Fri, 10 Dec 2021 11:50:10 -0500
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Michael Petlan <mpetlan@...hat.com>,
Ian Rogers <irogers@...gle.com>,
linux-perf-users <linux-perf-users@...r.kernel.org>
Subject: Re: [RFC] perf record: Disable debuginfod by default
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.
- FChE
Powered by blists - more mailing lists