public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/29959] New: Investigate parallel reader scalability Date: Tue, 03 Jan 2023 14:04:10 +0000 [thread overview] Message-ID: <bug-29959-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29959 Bug ID: 29959 Summary: Investigate parallel reader scalability Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Created attachment 14548 --> https://sourceware.org/bugzilla/attachment.cgi?id=14548&action=edit screen shot from gnuplot I was curious about the scalability of the parallel reader, so I built on gcc112, which reports 160 processors. I made a file like: maint time 1 file /tmp/gdb Then I ran: for j in $(seq 0 180); do echo ======= $j ; ./gdb/gdb -nh -quiet -iex "maint set worker-threads $j" < S; done I had it go over 160 just to see if that was interesting or not. To my surprise, the results don't seem to improve past N=8 or so. There are multiple possible explanations for this, but it would be worthwhile to find out exactly why. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-01-03 14:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-03 14:04 tromey at sourceware dot org [this message] 2023-01-03 14:04 ` [Bug symtab/29959] " tromey at sourceware dot org 2023-01-03 14:05 ` tromey at sourceware dot 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-29959-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).