Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 41718 invoked from network); 3 Sep 2009 16:03:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Sep 2009 16:03:42 -0000 Received: (qmail 91079 invoked by uid 500); 3 Sep 2009 16:03:42 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 91059 invoked by uid 500); 3 Sep 2009 16:03:42 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 91049 invoked by uid 99); 3 Sep 2009 16:03:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2009 16:03:42 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [66.111.4.25] (HELO out1.smtp.messagingengine.com) (66.111.4.25) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2009 16:03:31 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 873395B6D1 for ; Thu, 3 Sep 2009 12:03:10 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 03 Sep 2009 12:03:10 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=content-type:mime-version:subject:from:in-reply-to:date:content-transfer-encoding:message-id:references:to; s=smtpout; bh=bp6KgeG9ZmVJuJJ3W5NOQKNsdy8=; b=kUikkR5HkXoFaGNnXvpm3ytZvIXqNc7xWNGAkxQinmvBuicHad2SCRHyD9WkaU1rvXXd1axx2K3z0etP+IkWXBiKdtZodh1UG/hd0tacbe1hQhloWHBHQLo6pChjmXlwbbkwiJALQ5ZufWAM7vi+U2la6YnvCGmbMDbyYDhe5FA= X-Sasl-enc: yLHXdBCtEkg4xIex3d50M8TU/mogte8rmFbW98xeTka8 1251993789 Received: from [192.168.178.24] (pD9537513.dip.t-dialin.net [217.83.117.19]) by mail.messagingengine.com (Postfix) with ESMTPSA id A59BC65EDA for ; Thu, 3 Sep 2009 12:03:09 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v1075.2) Subject: Re: Ivy Performance From: Hans Dockter In-Reply-To: <6B4D8A42E536AC4EAC179B77DC162AB27935DA@atl-mail03.corp.int-silverpop.com> Date: Thu, 3 Sep 2009 18:02:56 +0200 Content-Transfer-Encoding: 7bit Message-Id: References: <67A198AA-0440-43B3-9275-A30F88B2A795@dockter.biz> <6B4D8A42E536AC4EAC179B77DC162AB27935DA@atl-mail03.corp.int-silverpop.com> To: ivy-user@ant.apache.org X-Mailer: Apple Mail (2.1075.2) X-Virus-Checked: Checked by ClamAV on apache.org On Sep 3, 2009, at 4:40 PM, Carlton Brown wrote: > The resolve task actually fetches artifacts into the local cache, so > you > would expect subsequent resolves of the same configuration to be much > faster (likewise with extended configurations, if they are not too > disjoint from the base configuration). > > If you observe that subsequent resolves don't benefit from previous > ones, it sounds as if you're somehow circumventing the cache > mechanism... perhaps defeating its effectiveness by setting the > useOrigin attribute, using a TTL, cleaning the cache between each > resolve, or using a distinct cache for each resolve. None of these > behaviors are enabled by default. > > I'd check the state of the cache after each resolve... if it isn't > getting populated with artifacts, or if it's getting wiped entirely, > there's your problem. Thanks for your reply. I should have mentioned that all artifacts are in the cache and are retrieved from the cache. But a resolve from a cache also easily takes more than a second. In the case of a second Ant Ivy resolve this number shrinks in our examples to something like 200ms. Therefore I was wondering what optimization is taking place here and how to use this for our build system. - Hans -- Hans Dockter Gradle Project Manager http://www.gradle.org