Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 35061 invoked from network); 13 Jun 2004 13:04:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 13 Jun 2004 13:04:16 -0000 Received: (qmail 13986 invoked by uid 500); 13 Jun 2004 13:04:16 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 13868 invoked by uid 500); 13 Jun 2004 13:04:15 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 13848 invoked by uid 99); 13 Jun 2004 13:04:15 -0000 Received: from [217.42.133.41] (HELO coderage.org) (217.42.133.41) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sun, 13 Jun 2004 06:04:15 -0700 Received: from CodeRage.ORG (localhost [IPv6:::1]) by coderage.org (8.12.9+Sun/8.12.9) with ESMTP id i5DCLEhK014407 for ; Sun, 13 Jun 2004 13:21:29 +0100 (WEST) Message-ID: <40CC46B9.2020306@CodeRage.ORG> Date: Sun, 13 Jun 2004 13:21:13 +0100 From: Michael Davey User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040116 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gump code and data Subject: Re: (CVS & SVN) Re: [VOTE] retire java gump References: <40C5DA63.1050801@jicarilla.org> <40C5E454.3030503@CodeRage.ORG> <13d101c44d76$16acce80$03bfea43@sybase.com> In-Reply-To: <13d101c44d76$16acce80$03bfea43@sybase.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Adam R. B. Jack wrote: >We could take the opportunity to: > >1) Move Gump (Python) core to SVN >2) Move Gump Metadata to a separate CVS repository [to move to SVN one day >in the future, when all ASF committer are "comfortable" w/ SVN]. > >We could leave the current repository as is, tagged but even CVS HEAD >stable, for automated Gumps out there that depend upon things there. > > +1 >>My main concern >>at the moment is that python gump seems a /lot/ slower than java gump on >>my under-powered, over-worked Sun Ultra 5. On that machine a Java gump >>run would take in the order of 19 hours. I started a Python gump run on >>the 6th June at 2.33pm local time and it still isn't finished (as of the >>8th June at 5.05pm). >> >> > >Performance has become my bugbear w/ this stuff. I just don't get the >language well enough to be able to crack it. > I've just completed another full gump run (same definition as the public gumps). I started the run at Thu Jun 10 08:16:23 WEST 2004 but Gump says the run started at Thu, 10 Jun 2004 08:23:40 (WEST), some 7 minutes later. Gump says the run finished at Sat, 12 Jun 2004 21:28:52 (WEST) but the process actually terminated at Sun Jun 13 02:26:12 WEST 2004, some 5 hours later. What was Gump doing during this time? I also tried gumping just ant, which took 4 hours. > >FWIIW: I find small (50 project) workspaces zip by, but large ones (500+) >seem to creep. > >BTW: How many projects do you have in this workspace? What is the purpose of >it? Do you "trim/tailor" the project sequence by passing "myproj*" project >masks? > >BTW: Do you use forrest batch, or not forrest xdocs? > > I think I can answer that one by saying "I don't know - the default". Could you point me to some docs that describe how to set up the other? -- Michael --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org