Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Performance of fileset related operations with a large number of
 files
Date: Thu, 19 Jan 2006 16:18:02 -0800
Message-ID: <8E08C7734517F147B0E60F065B5D7155012E054F@vcebe101.NOE.Nokia.com>
Thread-Topic: Performance of fileset related operations with a large number of
 files
Thread-Index: AcYdVvn2eYDpP8WCTg+vfcvOQru9xA==
From: <Paul.Mackay@nokia.com>
To: <dev@ant.apache.org>

Hello,

I have been trialling Ant as a driver for a large scale build execution.
The preparation before the build involves copying and unzipping >100,000
files spread across >20,000 directories. When using Ant's built in copy
task with filesets selecting large parts of these files, a long time is
spent building the list of files to copy, which also takes a lot of
memory. This is my understanding of how Ant works with filesets after
browsing the source.=20

Is there any way to avoid this high memory usage and time spent building
a list?

Has there ever been any consideration of refactoring the way Ant
processes filesets and similar constructs such that each selected file
is processed once read in an iterative fashion, rather than building a
complete list and then processing?

thanks

paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org