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:17:15 +0000 [thread overview] Message-ID: <bug-99105-4-hJWWACUAZQ@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 #7 from Jan Hubicka <hubicka at ucw dot cz> --- > > Because user apps may do funny thins with stdio such as they do with > > malloc. Fewer library stuff we rely on, the less likely we will hit the > > problems. So I am not sure if simply fixing i/o isn't better approach, > > but I do not know. > > Sure. With the patch, we don't rely on any glibc feature. We will just > use a default read/write IO (which uses a buffering internally). Well, buffered i/o is library feature :) > > 2727 gcda files, 44MB overall, 4MB xz compressed tar file. > > I am actually surprised that the file count is quite small. Firefox has > > more... > > To be honest, it's very small file size. I would expect these files should > definitely live in a page cache. For Firefox it is 2500 gcda files, 75MB overall, 6MB compressed. > > What type of disk do you use? /dev/nvme0n1 7QG00HVT Seagate FireCuda 520 SSD ZP1000GM30002 1 1.00 TB / 1.00 TB 512 B + 0 B STNSC014 (it is our new zen3 machine) Honza
next prev parent reply other threads:[~2021-02-15 15:17 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 [this message] 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 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-hJWWACUAZQ@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: linkBe 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).