Ullrich was kind enough to provide me data gathered by
my own performance listener, which shows timings for
tasks as well as targets:
Timing by tasks in Ant 1.6.2: in Ant 1.6.5
----------- ------ ------ ---------- ----------- ------
19.578,0 ms 175,2% 24x antcall 62.235,0 ms 189,0%
5.638,0 ms 50,5% 434x see.get 6.308,0 ms 19,2%
1.957,0 ms 17,5% 25x import 14.238,0 ms 43,2%
1.269,0 ms 11,4% 15131x property 11.775,0 ms 35,8%
563,0 ms 5,0% 43x delete 608,0 ms 1,8%
93,0 ms 0,8% 101x dirname 221,0 ms 0,7%
47,0 ms 0,4% 1x tstamp 47,0 ms 0,1%
30,0 ms 0,3% 25x presetdef 16,0 ms 0,0%
15,0 ms 0,1% 430x basename 453,0 ms 1,4%
0,0 ms 0,0% 78x mkdir 64,0 ms 0,2%
11.172,0 ms 100,0% 1x TOTAL 32.922,0 ms 100,0%
So this data seems to indicate a significant slow down of
<import> and <property> more than <antcall>. The combined
slow down of these 2 tasks amounts to 23.2 seconds which
is pretty much the whole slow down. <antcall>'s own perf
data is masked by that of the nested tasks, but most
likely peanuts.
Does anybody have any clue to why these two tasks got so
much slower in between patch releases? The slow down of
<import> is more dramatic than <property>, since for
25 calls 'only'.
15K <property> calls might be unusual a bit, but still.
Thanks, --DD
PS: the 9,987.65 are for a German locale, reverse of US convention.
PPS: Percentages go above 100% because consider nested tasks too.
PPPS: the task execution count was identical in 1.6.5 (not shown)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
