From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27557] New: Use threading at sub-file level
Date: Wed, 10 Mar 2021 13:36:25 +0000 [thread overview]
Message-ID: <bug-27557-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27557
Bug ID: 27557
Summary: Use threading at sub-file level
Product: dwz
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
Using parallelism we can speed up dwz.
We can introduce parallelism at file-level. PR25951 is about that. The
problem there is that doing so also increases memory footprint.
We can also use parallelism at sub-file level: we still operate on one file at
a time (so we don't increase memory footprint), but try to use threads to speed
things up.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-10 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 13:36 vries at gcc dot gnu.org [this message]
2021-03-10 14:31 ` [Bug default/27557] " vries at gcc dot gnu.org
2021-03-10 15:11 ` vries at gcc dot gnu.org
2021-03-12 10:56 ` vries at gcc dot gnu.org
2021-03-12 12:35 ` vries at gcc dot gnu.org
2021-03-12 12:39 ` vries 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-27557-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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: 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).