Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:31265 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7656 invoked by uid 1010); 25 Jul 2007 15:37:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 7641 invoked from network); 25 Jul 2007 15:37:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2007 15:37:32 -0000 X-Host-Fingerprint: 82.155.79.25 unknown Received: from [82.155.79.25] ([82.155.79.25:12887] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F3/80-02163-93E67A64 for ; Wed, 25 Jul 2007 11:37:29 -0400 Message-ID: To: internals@lists.php.net References: <000301c7ce41$5fc5e7b0$0100a8c0@pc07653> Date: Wed, 25 Jul 2007 16:37:25 +0100 Lines: 35 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-RFC2646: Format=Flowed; Response X-Posted-By: 82.155.79.25 Subject: Re: multi-threaded run-tests.php From: nlopess@php.net ("Nuno Lopes") So here it is my first attempt: http://gcov.php.net/~nlopess/multi_threaded_run_tests.txt WARNING: The patch is ugly and the output of the script isn't the prettiest. Anyway, for automated testing seems to be good enough. Nuno P.S.: after this little hack, I also start to feel that run-tests.php should be rewritten :P ""Nuno Lopes"" wrote: > Hi, > > Recently we have moved http://gcov.php.net to a new (and much faster) > server. This allowed us to reduce the time to build all branches to "just" > 2 days (compared with almost one week that would take previously). > However I'm still not happy :P The server has 2x2 CPU cores and I would > like to use them :) Currently I can speed-up the make process, because it > can be parallelized (with -j xx). But the major time is still spent with > run-tests.php. > > So, what I would like to propose is a multi-threaded version of > run-tests.php. We could spawn x processes (configurable) and one of them > would test y extensions (I think it's better to have each extension's > tests tested serially or they may break, because they may use the same > resources: BDs, files, etc..). > > Any comments? > > Thanks, > Nuno