public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/99105] profile streaming scales poorly to projects with many source files
Date: Mon, 15 Feb 2021 15:21:19 +0000	[thread overview]
Message-ID: <bug-99105-4-BFa3EekPUI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99105-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99105

--- Comment #9 from Jan Hubicka <hubicka at ucw dot cz> ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99105
> 
> --- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
> This is what I see for GCC PGO in train stage. It's from perf top:
> 
>    4.33%  cc1plus                          [.] __gcov_indirect_call_profiler_v4
>                                  ◆
>    2.28%  cc1plus                          [.] __gcov_topn_values_profiler     
>                                  ▒
>    0.85%  cc1plus                          [.] ggc_internal_alloc              

Yep, this is usual profile I see.  Perhaps you want to try profile "make check"
> 
> In the case of GCC, we emit 500 .gcda files.
> 
> @Honza: Can you please test my patch that uses glibc buffered I/O if it helps?

I can give it a try later this week (I would like to collect some data on
performance first)

Honza

  parent reply	other threads:[~2021-02-15 15:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 13:46 [Bug gcov-profile/99105] New: " hubicka at gcc dot gnu.org
2021-02-15 13:56 ` [Bug gcov-profile/99105] " hubicka at gcc dot gnu.org
2021-02-15 13:58 ` marxin at gcc dot gnu.org
2021-02-15 14:19   ` Jan Hubicka
2021-02-15 13:59 ` marxin at gcc dot gnu.org
2021-02-15 14:19 ` hubicka at ucw dot cz
2021-02-15 14:38 ` marxin at gcc dot gnu.org
2021-02-15 14:50 ` hubicka at ucw dot cz
2021-02-15 14:56 ` marxin at gcc dot gnu.org
2021-02-15 15:17 ` hubicka at ucw dot cz
2021-02-15 15:18 ` marxin at gcc dot gnu.org
2021-02-15 15:21   ` Jan Hubicka
2021-02-15 15:21 ` hubicka at ucw dot cz [this message]
2021-02-15 15:21 ` marxin at gcc dot gnu.org
2021-02-15 15:23 ` marxin at gcc dot gnu.org
2021-02-15 15:32   ` Jan Hubicka
2021-02-15 15:32 ` hubicka at ucw dot cz
2021-02-15 16:12 ` hubicka at ucw dot cz
2021-02-15 20:20 ` [Bug gcov-profile/99105] [11 regression] " hubicka at gcc dot gnu.org
2021-02-15 20:40 ` hubicka at gcc dot gnu.org
2021-02-16 10:31 ` marxin at gcc dot gnu.org
2021-02-16 13:57 ` marxin at gcc dot gnu.org
2021-03-04 15:22 ` cvs-commit at gcc dot gnu.org
2021-03-04 15:23 ` marxin at gcc dot gnu.org

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=bug-99105-4-BFa3EekPUI@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).