Addition of an ant target called run performance test. This test will run a simple timed application. (remote and local tests)
Addition of an ant target called run performance test.
This test will run a simple timed application. (remote and local tests)

These are the command line options of the performanceTest :

bash-3.00$ ./build runPerformanceTest -Dn=10
Buildfile: /user/vbodnart/workspace/ProActive_New/compile/build.xml

runPerformanceTest:
     [echo] Starting the performance test.
     [java] usage: Performance test options
     [java]  -c,--compareCurrentWith     Specify the version to compare with. By
     [java]                              default the latest precedent version is used. This option invalidates the
     [java]                              x option.
     [java]  -n,--nbRuns                 Specify the number of runs. Default is 5.
     [java]  -o,--outputDir              Specify the output directory.
     [java]  -p,--printCurrentVersion    Prints the current ProActive version.
     [java]  -x,--compareAmount          Specify the number of precedent consecutive
     [java]                              versions to compare with the current. Default is 1 (the latest precedent
     [java]                              version).

Be aware that the last option supposes that the consecutive precedent versions output files are already in the output directory.
For more stable tests just make more runs per tests (the average time for each timer is then computed).

git-svn-id: 9146c88ff6d39b48099bf954d15d68f687b3fa69@5161 28e8926c-6b08-0410-baaa-805c5e19b8d6

jrochas/scale-proactive,lpellegr/programming,mnip91/programming-multiactivities,PaulKh/scale-proactive,paraita/programming,acontes/scheduling,ow2-proactive/programming,mnip91/programming-multiactivities,fviale/programming,paraita/programming,acontes/programming,mnip91/proactive-component-monitoring,fviale/programming,acontes/scheduling,ow2-proactive/programming,lpellegr/programming,lpellegr/programming,acontes/programming,lpellegr/programming,PaulKh/scale-proactive,acontes/scheduling,fviale/programming,paraita/programming,paraita/programming,acontes/programming,mnip91/proactive-component-monitoring,jrochas/scale-proactive,jrochas/scale-proactive,paraita/programming,acontes/scheduling,jrochas/scale-proactive,PaulKh/scale-proactive,mnip91/programming-multiactivities,paraita/programming,fviale/programming,acontes/programming,acontes/programming,lpellegr/programming,mnip91/proactive-component-monitoring,fviale/programming,ow2-proactive/programming,jrochas/scale-proactive,mnip91/programming-multiactivities,acontes/programming,acontes/programming,PaulKh/scale-proactive,jrochas/scale-proactive,mnip91/proactive-component-monitoring,ow2-proactive/programming,ow2-proactive/programming,PaulKh/scale-proactive,mnip91/programming-multiactivities,acontes/scheduling,ow2-proactive/programming,jrochas/scale-proactive,fviale/programming,mnip91/programming-multiactivities,PaulKh/scale-proactive,mnip91/proactive-component-monitoring,lpellegr/programming,acontes/scheduling,mnip91/proactive-component-monitoring,PaulKh/scale-proactive,acontes/scheduling