From 8fb1c2afaf6b368f3ef981f28fb40042fd300d9b Mon Sep 17 00:00:00 2001 From: Steve Loughran Date: Wed, 14 Feb 2007 15:43:08 +0000 Subject: [PATCH] thread-safe edition git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@507587 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/CoreTasks/parallel.html | 140 +++++++++++++++++----------- 1 file changed, 88 insertions(+), 52 deletions(-) diff --git a/docs/manual/CoreTasks/parallel.html b/docs/manual/CoreTasks/parallel.html index 3eb78137e..b97fca1da 100644 --- a/docs/manual/CoreTasks/parallel.html +++ b/docs/manual/CoreTasks/parallel.html @@ -26,8 +26,32 @@

Parallel

Description

-

Parallel is a container task - it can contain other Ant tasks. Each nested -task within the parallel task will be executed in its own thread.

+

+ Executes nested tasks in parallel with no guarantees of thread safety. + Every task will run in its own thread, with the likelihood of + concurrency problems scaling with the number of CPUs on the host system. +

+

Warning: While the Ant core is believed to be thread safe, no such + guarantees are made about tasks, which are not tested for thread safety during + Ant's test process. + Third party tasks may or may not be thread safe, and some of Ant's core tasks, such as + <javac> are definitely not re-entrant. This is because they use libraries that + were never designed to be used in a multithreaded environment. +

+

+ The primary use case for <parallel> is to run external programs + such as an application server, and the JUnit or TestNG test suites at the + same time. Anyone trying to run large Ant task sequences in parallel, such + as javadoc and javac at the same time, is implicitly taking on the task + of identifying and fixing all concurrency bugs the tasks that they run. + +

+

+ Accordingly, while this task has uses, it should be considered an advanced + task which should be used in certain batch-processing or testing situations, + rather than an easy trick to speed up build times on a multiway CPU. +

+

Parameters

@@ -43,14 +67,9 @@ task within the parallel task will be executed in its own thread.

+(Java 1.4+) - - - - - @@ -62,28 +81,29 @@ task within the parallel task will be executed in its own thread.

at that point without waiting for any other tasks to complete. + + + + +
threadsPerProcessor Maximum number of threads to use per available processor -(Requires JDK 1.4) No, defers to threadCount
pollIntervalCurrently has no effectNo, default is 1000
timeout Number of milliseconds before execution is terminated No
pollIntervalCurrently has no effectNo, default is 1000

Parallel tasks have a number of uses in an Ant build file including:

-

Care must be taken when using multithreading to ensure the tasks within the -threads do not interact. For example, two javac compile tasks which write -classes into the same destination directory may interact where one tries to -read a class for dependency information while the other task is writing the -class file. Be sure to avoid these types of interactions within a -<parallel> task

-

Any valid Ant task may be embedded within a -parallel task, including other parallel tasks.

+parallel task, including other parallel tasks, though there is no guarantee that +the tasks will be thread safe in such an environment.

-

Note that while the tasks within the parallel task are being run, the main +

While the tasks within the parallel task are being run, the main thread will be blocked waiting for all the child threads to complete. If -execution is terminated by a timeout or a nested task failure when the failonany +execution is terminated by a timeout or a nested task failure when the +failonany flag is set, the parallel task will complete without waiting for other nested tasks to complete in other threads.

@@ -96,7 +116,7 @@ all threads have completed. In this situation, the parallel task will also fail. sequential task to define sequences of tasks to be executed on each thread within the parallel block

-

The threadCount attribute can be used to place a maximum number of available +

The threadCount attribute can be used to place a maximum number of available threads for the execution. When not present all child tasks will be executed at once. When present then the maximum number of concurrently executing tasks will not exceed the number of threads specified. Furthermore, each task will be @@ -104,16 +124,18 @@ started in the order they are given. But no guarantee is made as to the speed of execution or the order of completion of the tasks, only that each will be started before the next.

-

If you are using J2RE 1.4 or later you can also use the threadsPerProcessor +

If you are using Java 1.4 or later you can also use the threadsPerProcessor and the number of available threads will be the stated multiple of the number of processors (there is no affinity to a particular processor however). This will -override the value in threadCount. If threadsPerProcessor is specified using -any version prior to 1.4 then the value in threadCount will be used as is.

- -

When using threadCount and threadsPerProcessor care should be taken to ensure -that the build does not deadlock. This can be caused by tasks such as waitFor -taking up all available threads before the tasks that would unlock the waitfor -would occur. This is not a repalcement for Java Language level thread +override the value in threadCount. If threadsPerProcessor +is specified on any older JVM, then the value in threadCount will be used as is.

+ +

When using threadCount and threadsPerProcessor + care should be taken to ensure that the build does not deadlock. + This can be caused by tasks such as waitfor + taking up all available threads before the tasks that would unlock the + waitfor +would occur. This is not a replacement for Java Language level thread semantics and is best used for "embarassingly parallel" tasks.

@@ -141,57 +163,71 @@ terminated from Ant. By using <daemons> such servers do not h <wlrun ... > <sequential> <sleep seconds="30"/> - <junit ... > + <junit fork="true" forkmode="once" ... > <wlstop/> </sequential> </parallel>

This example represents a typical pattern for testing a server application. -In one thread the server is started (the wlrun task). The other thread consists -of a three tasks which are performed in sequence. The sleep task is used to +In one thread the server is started (the <wlrun> task). +The other thread consists +of a three tasks which are performed in sequence. The <sleep> task is used to give the server time to come up. Another task which is capable of validating -that the server is available could be used in place of the sleep task. The -test harness is then run. Once the tests are complete, the server is stopped -(using wlstop in this example), allowing both threads to complete. The -parallel task will also complete at this time and the build will then +that the server is available could be used in place of the <sleep> task. The +<junit> test harness then runs, again in its own JVM. Once the tests are complete, the server is stopped +(using <wlstop> in this example), allowing both threads to complete. The +<parallel> task will also complete at this time and the build will then continue.

 <parallel>
-  <javac ...> <!-- compiler servlet code -->
+  <javac fork="true"...> <!-- compiler servlet code -->
   <wljspc ...> <!-- precompile JSPs -->
 </parallel>

This example shows two independent tasks being run to achieve better resource utilization during the build. In this instance, some servlets are being -compiled in one thead and a set of JSPs is being precompiled in another. As -noted above, you need to be careful that the two tasks are independent, both in +compiled in one thead and a set of JSPs is being precompiled in another. Developers +need to be careful that the two tasks are independent, both in terms of their dependencies and in terms of their potential interactions in -Ant's external environment.

+Ant's external environment. Here we set fork="true" for the +<javac> task, so that it runs in a new process; +if the <wljspc> task used the javac compiler in-VM +(it may), concurrency problems may arise. +

+ + <macrodef name="dbpurge"> + <attribute file="file"/> + <sequential> + <java jar="utils/dbpurge.jar" fork="true" > + <arg file="@{file} /> + </java> + </sequential> +</macrodef> + <parallel threadCount='4'> - <ant target='TargetThatConsumesLotsOfCPUTimeAndMemory'> - <param name='file' value='one.txt'/> - </ant> - <ant target='TargetThatConsumesLotsOfCPUTimeAndMemory'> - <param name='file' value='two.txt'/> - </ant> - <ant target='TargetThatConsumesLotsOfCPUTimeAndMemory'> - <param name='file' value='three.txt'/> - </ant> + <dbpurge file="db/one" /> + <dbpurge file="db/two" /> + <dbpurge file="db/three" /> + <dbpurge file="db/four" /> + <dbpurge file="db/five" /> + <dbpurge file="db/six" /> + <dbpurge file="db/seven" /> + <dbpurge file="db/eight" /> <!-- repeated about 40 times --> </parallel>

This example represents a typical need for use of the threadCount and threadsPerProcessor attributes. Spinning up all 40 of those tasks could cripple -the JVM for memory and the CPU for available time. By limiting the number of -concurrent executions you can get the task done in about the same assuming -infinite memory time without needing infinite memory. This is also a good +the system for memory and CPU time. By limiting the number of +concurrent executions you can reduce contention for CPU, memory and disk IO, +and so actually finish faster. This is also a good candidiate for use of threadCount (and possibly threadsPerProcessor) because -each task (in this hypothetical case) is independent and has no dependencies on +each task is independent (every new JVM is forked) and has no dependencies on the other tasks.