public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27507] New: [dwz] Low-mem mode slowness
Date: Wed, 03 Mar 2021 15:04:38 +0000	[thread overview]
Message-ID: <bug-27507-11298@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27507

            Bug ID: 27507
           Summary: [dwz] Low-mem mode slowness
           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: ---

Low-mem was originally advertised with:
...
commit d3b509689e17cd4885e0dfb9ad777e6337297282
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue May 29 19:00:58 2012 +0200

    Implement special low_mem mode, which roughly halves amount of
    needed RAM at the expense of small slowdown on very large
    inputs (more than -l COUNT DIEs).  Give up if input has more than
    -L COUNT DIEs.
...

Now consider the test-case Checker.so.debug, ~48 million DIEs, .debug_info
~0.5GB:
...
$ ./src/contrib/bytes-per-die.sh $f
11.15   size: 542547271 nr_dies: 48634711
...

We compare normal and low-mem mode:
...
+ ../measure/time.sh ./dwz debug/Checker.so.debug -o debug/Checker.so.debug.z
-lnone -Lnone --no-odr
maxmem: 5912860
real: 69.10
user: 65.82
system: 3.27
+ ../measure/time.sh ./dwz debug/Checker.so.debug -o debug/Checker.so.debug.z
-l0 -Lnone --no-odr
maxmem: 3048072
real: 135.65
user: 133.19
system: 2.40
...

The memory savings is correct, roughly 50%. But the increase in computation
time is almost a factor two.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2021-03-03 15:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-27507-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).