Recent changes to Home

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 23:12:17 -0000

--- v16
+++ v17
@@ -16,6 +16,6 @@

 [Different versions of the Timer](http://sourceforge.net/p/anttimer/wiki/Versions/)

-[How I refactored a slow build script](http://sourceforge.net/p/anttimer/wiki/Story/)
+[How to refactor a slow build script](http://sourceforge.net/p/anttimer/wiki/Story/)

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:31:27 -0000

--- v15
+++ v16
@@ -12,10 +12,10 @@
 4. after the build is done, you will find an anttimer subfolder.
 5. open the anttimer/index.html in a browser, and drill down the report.

-[More about the HTML report being generated]https://sourceforge.net/p/anttimer/wiki/Report%20views/)
+[More about the HTML report being generated](http://sourceforge.net/p/anttimer/wiki/Report%20views/)

-[Different versions of the Timer](https://sourceforge.net/p/anttimer/wiki/Versions/)
+[Different versions of the Timer](http://sourceforge.net/p/anttimer/wiki/Versions/)

-[How I refactored a slow build script](https://sourceforge.net/p/anttimer/wiki/Story/)
+[How I refactored a slow build script](http://sourceforge.net/p/anttimer/wiki/Story/)

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:30:55 -0000

--- v14
+++ v15
@@ -12,7 +12,10 @@
 4. after the build is done, you will find an anttimer subfolder.
 5. open the anttimer/index.html in a browser, and drill down the report.

-[More about the HTML report being generated](https://sourceforge.net/p/anttimer/wiki/Report%20views/)
+[More about the HTML report being generated]https://sourceforge.net/p/anttimer/wiki/Report%20views/)
+
+[Different versions of the Timer](https://sourceforge.net/p/anttimer/wiki/Versions/)
+
+[How I refactored a slow build script](https://sourceforge.net/p/anttimer/wiki/Story/)

-

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:28:45 -0000

--- v13
+++ v14
@@ -12,5 +12,7 @@
 4. after the build is done, you will find an anttimer subfolder.
 5. open the anttimer/index.html in a browser, and drill down the report.

+[More about the HTML report being generated](https://sourceforge.net/p/anttimer/wiki/Report%20views/)

+

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:27:02 -0000

--- v12
+++ v13
@@ -12,52 +12,5 @@
 4. after the build is done, you will find an anttimer subfolder.
 5. open the anttimer/index.html in a browser, and drill down the report.

-Report
-------
-
-#### Chronological ####
-
-[[img src=chronological.PNG]]
-
-This view illustrates the hierarchy of your build, with subbuild and targets as branches in the tree, and tasks as leaves.
-
-Each line shows
-1. a **bar** representing the relative weight of the line and it's children in the total build.
-2. the **time taken as % of the total build time**. Due to rounding errors or filtering of short tasks (see Timer or MinimumTimer) the sum of the percentages can be considerably smaller than 100%.
-3. the **task/target name**
-4. if available, the **project** is shown between ().
-5. next you see the **ant source code** of the subbuild/target/task. It's a link, so you can click through to an HTML version of the ant build files.
-6. finally, there might be a link to the **messages** the ant build logged while working on this subbuild/target/task. The MinimumTimer will not write this info.
-
-*The image above illustrates that, after some basic set-up, most time is spent in the subbuild of project Act.*
-
-#### Slowest first ####
-
-[[img src=slowest_first.PNG]]
-
-The same information is show, but not chronologically. The first branches are the slowest ones.
-
-*The image above shows that the subbuild Act takes most time, but the target -commons-autoupdate takes a whopping 47% of the total build time. In this case, this task updates the copy of the enterprise repository on the local disk of the build machine.*
-
-#### Toppers ####
-
-[[img src=toppers.PNG]]
-
-This view is the most interesting to actually do something about the speed of your build.
-It shows the tasks (only tasks!) that take the most time, because they are slow or because they are executed many times.

-Each line in the table shows:
-1. **Min**: fastest time of the task, in milliseconds.
-2. **Max**: slowest time of the task, in milliseconds.
-3. **Average** : average time, in milliseconds.
-4. **Count** : number of times this specific task has been executed.
-5. **Total** : sum of all execution times, , in milliseconds.
-6. **% of build**: total time of this task compared to the total of the build.
-7. **Name** : link to the source code of the task.
-
-*In the image above, you see that the top 8 tasks contain 2 subversion tasks, 1 jasperreports compile, and 3 ivy tasks. Only one is a compile task. A ivy:cachepath task is being executed 41 times!*
-
-Versions of the Timer
----------------------
-

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:16:38 -0000

--- v11
+++ v12
@@ -29,11 +29,15 @@
 5. next you see the **ant source code** of the subbuild/target/task. It's a link, so you can click through to an HTML version of the ant build files.
 6. finally, there might be a link to the **messages** the ant build logged while working on this subbuild/target/task. The MinimumTimer will not write this info.

+*The image above illustrates that, after some basic set-up, most time is spent in the subbuild of project Act.*
+
 #### Slowest first ####

 [[img src=slowest_first.PNG]]

 The same information is show, but not chronologically. The first branches are the slowest ones.
+
+*The image above shows that the subbuild Act takes most time, but the target -commons-autoupdate takes a whopping 47% of the total build time. In this case, this task updates the copy of the enterprise repository on the local disk of the build machine.*

 #### Toppers ####

@@ -50,7 +54,9 @@
 4. **Count** : number of times this specific task has been executed.
 5. **Total** : sum of all execution times, , in milliseconds.
 6. **% of build**: total time of this task compared to the total of the build.
-7. **Name** : link to the source code of the task;
+7. **Name** : link to the source code of the task.
+
+*In the image above, you see that the top 8 tasks contain 2 subversion tasks, 1 jasperreports compile, and 3 ivy tasks. Only one is a compile task. A ivy:cachepath task is being executed 41 times!*

 Versions of the Timer
 ---------------------

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:08:14 -0000

--- v10
+++ v11
@@ -37,6 +37,20 @@

 #### Toppers ####

+[[img src=toppers.PNG]]
+
+This view is the most interesting to actually do something about the speed of your build.
+It shows the tasks (only tasks!) that take the most time, because they are slow or because they are executed many times.
+
+
+Each line in the table shows:
+1. **Min**: fastest time of the task, in milliseconds.
+2. **Max**: slowest time of the task, in milliseconds.
+3. **Average** : average time, in milliseconds.
+4. **Count** : number of times this specific task has been executed.
+5. **Total** : sum of all execution times, , in milliseconds.
+6. **% of build**: total time of this task compared to the total of the build.
+7. **Name** : link to the source code of the task;

 Versions of the Timer
 ---------------------

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:04:41 -0000

--- v9
+++ v10
@@ -15,7 +15,7 @@
 Report
 ------

-### Chronological ###
+#### Chronological ####

 [[img src=chronological.PNG]]

@@ -29,13 +29,13 @@
 5. next you see the **ant source code** of the subbuild/target/task. It's a link, so you can click through to an HTML version of the ant build files.
 6. finally, there might be a link to the **messages** the ant build logged while working on this subbuild/target/task. The MinimumTimer will not write this info.

-### Slowest first ###
+#### Slowest first ####

 [[img src=slowest_first.PNG]]

 The same information is show, but not chronologically. The first branches are the slowest ones.

-### Toppers ###
+#### Toppers ####

 Versions of the Timer

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:03:52 -0000

--- v8
+++ v9
@@ -23,11 +23,11 @@

 Each line shows
 1. a **bar** representing the relative weight of the line and it's children in the total build.
-+ the **time taken as % of the total build time**. Due to rounding errors or filtering of short tasks (see Timer or MinimumTimer) the sum of the percentages can be considerably smaller than 100%.
-+ the **task/target name**
-+ if available, the **project** is shown between ().
-+ next you see the **ant source code** of the subbuild/target/task. It's a link, so you can click through to an HTML version of the ant build files.
-+ finally, there might be a link to the **messages** the ant build logged while working on this subbuild/target/task. The MinimumTimer will not write this info.
+2. the **time taken as % of the total build time**. Due to rounding errors or filtering of short tasks (see Timer or MinimumTimer) the sum of the percentages can be considerably smaller than 100%.
+3. the **task/target name**
+4. if available, the **project** is shown between ().
+5. next you see the **ant source code** of the subbuild/target/task. It's a link, so you can click through to an HTML version of the ant build files.
+6. finally, there might be a link to the **messages** the ant build logged while working on this subbuild/target/task. The MinimumTimer will not write this info.

 ### Slowest first ###

WikiPage Home modified by Vette Pinda

Vette Pinda — Wed, 06 Feb 2013 22:03:03 -0000

--- v7
+++ v8
@@ -31,6 +31,10 @@

 ### Slowest first ###

+[[img src=slowest_first.PNG]]
+
+The same information is show, but not chronologically. The first branches are the slowest ones.
+
 ### Toppers ###