This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 5.0 beta ] [ JDK VERSION : 1.4.2_xx ] Building a large project (900 files) using a custom Ant script that contains a lot of tasks that fork the VM takes around 40-50% more than in NB 4.1. It used to take 8-9 minutes and now takes 12 minutes.
Not an enhancement, this is a defect! Thanks for reporting that!
I don't think anything of significance has changed in the Ant module. Could be due to changes in AntLogger impls. Any profile data for the hotspots? Have you tried using the same version of Ant (e.g. 1.6.5) in both cases to rule that out as a cause?
Can hardly set a target milestone without information to reproduce or profile data.
>> ------- Additional comments from jglick Fri Sep 30 01:52:43 +0000 2005 ----- >> I don't think anything of significance has changed in the Ant module. Could >> be due to changes in AntLogger impls. Any profile data for the hotspots? How can I profile the NetBeans build process? >> Have you tried using the same version of Ant (e.g. 1.6.5) in both cases to >> rule that out as a cause? Using Ant 1.6.5 from the command line takesa round 8-9 minutes. It definitely has something to do with NB (maybe there are more threads now or threads with a higher priority?). BTW, do Ant builds run in a thread with a higher priority? I think they should :-)
"How can I profile the NetBeans build process?" - well, with a profiler. Someone will have to do it, maybe me if I can find the time. More critical now is a test case which is known to demonstrate the problem reliably, as well as any info about whether the problem is confined to Windows or is cross-platform. Ant builds do not run with a special priority. If anything, a *lower* priority would be appropriate (so that the rest of the UI is responsive while a long build is running). Note that thread priorities do not reliably do much, e.g. on Linux they are pretty useless.
Still awaiting steps to reproduce. Will close shortly if none provided.
If you can reproduce, please reopen with a test case of some sort.