From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DB3D93858D1E; Tue, 3 Jan 2023 14:04:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DB3D93858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672754650; bh=X236O3aAZaDHtXO3U7N57FJC3XBRVaEwVxNeKhsWMzQ=; h=From:To:Subject:Date:From; b=bWglBcserLd8g+4STkRmVpaLhFKGUJNgEMPc4fi09Ve2NgZq43J3D0YjvAWywzJpC QgUPiq5Tt3ULPwAfTtaKSFQ/yV1x5RlcMHRExWMtfWu6cBiyYyefpbS7EVGyEQ0boG SYL5igfbUrHH/eBheN+j2DoQTo3l0eaIIZFCSats= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/29959] New: Investigate parallel reader scalability Date: Tue, 03 Jan 2023 14:04:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29959 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=3D14548&action=3Ded= it 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 =3D=3D=3D=3D=3D=3D=3D $j ; ./gdb/gdb -nh -qu= iet -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=3D8 or so. There are multiple possible explanations for this, but it would be worthwhile to find out exactly why. --=20 You are receiving this mail because: You are on the CC list for the bug.=