public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Nathan Froyd <nfroyd@mozilla.com>,
	gcc-patches@gcc.gnu.org, jason@redhat.com
Subject: Re: [PATCH] parallelize g++ testing a bit more
Date: Mon, 20 Jun 2011 13:41:00 -0000	[thread overview]
Message-ID: <E649CF4C-5199-4B09-BEB1-4B3FF5B1E62E@comcast.net> (raw)
In-Reply-To: <ydd62o0rccg.fsf@manam.CeBiTec.Uni-Bielefeld.DE>

On Jun 20, 2011, at 4:06 AM, Rainer Orth wrote:
> I've got a patch to do this, prompted by the use of UltraSPARC-T2
> machines with 8 cores/8 strands which are quite slow on their own:
> 
> 	[build, testsuite, v3] Increase gcc, g++, gfortran and libstdc++-v3 testsuite parallelism
>        http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01633.html
> 
> but haven't yet incorporated Jakub's comments.

Yeah, I would not even consider a patch that was count based.  :-)  Ideally, what you want to do is to bin pack the completed in N seconds in B bins, where B is related to the physical number of cores.  The, there is _no_ extra overhead for subdivision on 1 core, and on 10,000 core, it still works, though, one is going to need slightly better 1 to B code.  Anyone know of a bin packer command line argument?  We don't care if it is slow, because we can bin pack every 10th run, and start with idealized times.  I would have contributed that sort of change a while ago, but didn't spot a bin packer.  I also did up code to pull from a single work list, but, dejagnu isn't structured to do that.  :-(  That would be the best solution, but is much more work.

  reply	other threads:[~2011-06-20 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 18:01 Nathan Froyd
2011-06-17 18:38 ` Jason Merrill
2011-06-18  2:06 ` Mike Stump
2011-06-20 11:11   ` Rainer Orth
2011-06-20 13:41     ` Mike Stump [this message]
2011-06-20 13:33   ` Jason Merrill
2011-06-20 14:02     ` Jakub Jelinek
2011-06-20 22:03       ` [PATCH] parallelize gcc, gfortran and libstdc++ testing some more Jakub Jelinek
2011-06-21  7:09         ` Jason Merrill
2011-06-22 13:55         ` Jeff Law

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=E649CF4C-5199-4B09-BEB1-4B3FF5B1E62E@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=nfroyd@mozilla.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).