From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Mike Stump <mikestump@comcast.net>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Jason Merrill <jason@redhat.com>,
Nathan Froyd <nfroyd@mozilla.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] parallelize gcc, gfortran and libstdc++ testing some more
Date: Wed, 22 Jun 2011 13:55:00 -0000 [thread overview]
Message-ID: <4E01F398.3060909@redhat.com> (raw)
In-Reply-To: <20110620210441.GG16443@tyan-ft48-01.lab.bos.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/20/11 15:04, Jakub Jelinek wrote:
> On Mon, Jun 20, 2011 at 03:54:59PM +0200, Jakub Jelinek wrote:
>> On Mon, Jun 20, 2011 at 09:28:56AM -0400, Jason Merrill wrote:
>>> On 06/17/2011 08:20 PM, Mike Stump wrote:
>>>> On Jun 17, 2011, at 10:47 AM, Nathan Froyd wrote:
>>>>> I've done a lot of g++-only testsuite runs lately
>>>>
>>>> I think it is reasonable to have even more of them, say, if you have 16 cores and just test c++... I wonder what the scaling is like as we approach larger N. :-)
>>>
>>> In my test runs, one of the libstdc++ batches (normal3) takes longer
>>> than any of the g++ batches, so breaking that up would be more
>>> effective for me. :)
>>
>> Yeah, certainly, libstdc++ needs more parallelization most.
>> But, as I wrote already to Rainer in Autumn, the methodology
>> for splitting things up should be on a fast box look at
>> the time spent in each of the parts as reported by dejagnu
>> in the log files, and split it to make the jobs roughly even
>> sized with not overcomplicated patterns.
>
> So, here is a patch that parallelizes the longest test chunks
> on x86_64-linux some more.
>
> libstdc++ testing is now split into 10 jobs, roughly equally sized
> (used to be 4), check-gcc testing is now split into 10 jobs too (used to
> be 7, but the new division attempts to be more balanced, fastest
> job takes for me 8 minutes and longest job takes 11), and check-gfortran
> is now run in 7 jobs instead of 4. This should make these more comparable
> e.g. to check-g++ chunks etc.
>
> Regtested on x86_64-linux, verified the merged *.sum files are identical.
> Ok for trunk?
>
> 2011-06-20 Jakub Jelinek <jakub@redhat.com>
>
> * Makefile.in (dg_target_exps): Set.
> (check_gcc_parallelize): Parallelize gcc testing into 10 jobs
> instead of 7, try to divide it more evenly.
>
> * Make-lang.in (check_gfortran_parallelize): Parallelize dg.exp
> into 6 jobs instead of 3.
>
> * testsuite/Makefile.am (check_DEJAGNU_normal_targets): Add
> check-DEJAGNUnormal[4-9].
> (check-DEJAGNU): Split into 10 jobs for parallel testing instead of 4.
> * testsuite/Makefile.in: Regenerated.
OK.
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOAfOYAAoJEBRtltQi2kC7fh4H/0ku6F+8rZEb0iy0zyr+KHUd
2qvA4BsXPcNs3xjwdqgrpvg9pM+6qXsEB8oEuaCBu7ndT8kCMPfnjaRP3otnl5ju
Maceyf0rZMDOUVYiYXYEstLMH+gljpraBU/n6UrvrXLLtZzna5yU6ZLwmPs1ngt/
+QQXWe34gRraEsLo4A9y5pcU69WnsVMdmrVKsRn/EnsLqSxClvmyWSaFrX0i5X4C
+NfQC3YQqiG0bjC6acCyfccHGJ+7tlyiafsyR0TDZPfGQLCwnRWNhm+A/GrTjYpY
nHbwhZ7sJef3gz9pLRm4qJ0OyMKqZo6c07Z43KdYIaIMQdjsh0CA3xfnd/vHSYQ=
=wO5+
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-06-22 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 18:01 [PATCH] parallelize g++ testing a bit more 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
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 [this message]
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=4E01F398.3060909@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mikestump@comcast.net \
--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).