From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add more parallelization to gdb.base testing
Date: Mon, 18 Jun 2012 16:48:00 -0000 [thread overview]
Message-ID: <20120618164823.GC19107@adacore.com> (raw)
In-Reply-To: <20120618163310.98BF71E136F@ruffy2.mtv.corp.google.com>
> This patch speeds up gdb testing at -j6 on my machine from 7mins to 4mins.
> I didn't want to get too carried away here, this felt like a good compromise.
Love the idea of adding more parallelization. FWIW, I run the AdaCore
testsuite at -j24 on my 3.5 year old quad-core. I start getting
diminishing benefits after -j20, but even at -j24, the machine is
still completely responsive. When doing testing with gdbserver or Qemu,
I usually use -j16 to -j20 to avoid some spurious timeouts. So I think
there is still room for more parallelization if we want to.
--
Joel
next prev parent reply other threads:[~2012-06-18 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 16:33 Doug Evans
2012-06-18 16:48 ` Joel Brobecker [this message]
2012-06-22 16:20 ` Tom Tromey
2012-06-18 16:35 Doug Evans
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=20120618164823.GC19107@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@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