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.
release 3.4 RC1 When I checkout a lot of files using JavaCVS cpu usage is pegged at 100% which doesn't seem to make much sense since this machine is around 500Mhz and the network pipe from the server isn't that fast to begin with. I suspect there is a bug at work..
can you get us a thread dump? so that we can figure out where the problem might lie? it's possible that it's not the checkout's fault but someone else tries to parse the already checked out sources ot similar. thanks.
There is filed similar issue #26113 for generic CVS filesystem. It might be, that the problem is the same, but I'm not sure. The thread dump would be valuable.
I'm not sure, whether it applies to this problem, but I've found some inefficiencies in the cache implementation in command-line module while fixing issue #25364. It needs to be found if the problem is in the checkout process or the file refresh and status storage process.
postponing to milestone 2
I'm solving this problem for command-line CVS integration. The improvements then will be ported to javacvs if possible.
I've tested checkout on JavaCVS after the fix of performance problems in vcscore module. There does not seem to be a problem. The CPU usage was kept around 30% and the IDE was responsive and usable during the checkout process. So I consider this as fixed, if there are some preformance problems persisting, please reopen with description. Thanks.
in recent trunk builds checkout seems fine for me... So I hope it's fixed.