From: Ben Woodard <woodard@redhat.com>
To: libabigail@sourceware.org
Subject: Re: Where are we?
Date: Wed, 21 Sep 2022 18:34:58 -0700 [thread overview]
Message-ID: <e0d9e480-2587-e3ac-a3af-c328e87b0cb5@redhat.com> (raw)
In-Reply-To: <22b479ce-09a5-52c6-24f9-d959310ce8f2@redhat.com>
oops I also meant to say. The performance work had some modest benefit.
The last time that I ran the test it was it took 23.5hrs on 18 cores.
I'm not down to 14 cores and it took 22hrs.
next prev parent reply other threads:[~2022-09-22 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 1:19 Ben Woodard
2022-09-22 1:34 ` Ben Woodard [this message]
2022-09-23 1:52 ` Where are we? (Sept 22 edition) Ben Woodard
2022-09-25 7:05 ` Dodji Seketeli
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=e0d9e480-2587-e3ac-a3af-c328e87b0cb5@redhat.com \
--to=woodard@redhat.com \
--cc=libabigail@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).