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.
This problem was initially submitted in issue #32065 by Andrew Gaydenko: "After VCS update command finished (judging by the status string), the IDE eats 100% CPU during some period. This period grows during working with the IDE from 4-5 sec to 15-20 sec."
Scheduling for 4.0, this is too much risky changes for NB 3.5 in this stage.
Martin, I must define more accurately _current_ time frames (after multiple changing in trunk :-). Update command (win 2000 CVS profile) has 3 phases: 1. with not zero net traffic - [send+receive] ~ 15 sec, 2. HDD activity - ~7 sec (it doesn't depends on the IDE, I think), CVS session is closed after this phase, 3. CPU 100% eating - ~18-20 sec :-(, and (this is the difference) only after this phase status string reports updating was done. _No_ any more CPU eating now after status string report! Last phase begins just after "Kill" button in UPDATE output panel is switched to "Close". Must I supply threads dumps for last phase? P.S. Sorry, I'm not english-speaker. Is there more suitable term for "CPU eating" phrase?
Hi Andrew, ThreadDumps are always valuaable, so go ahead and attach tmem, please. BTW: Most of us aren't English native speakers too:-) Main thing is to be able communicate and understand
Daniel, Martin, During last month many related issues were fixed. From my point of view, the issue may be closed - I don't notice cpu eating period growth.
I've made several various optimizations of status update after all commands and update after checkout/update commands. However there might be some more optimizations possible. QA please let me know whether the current state is acceptable or whether it needs some more tunning.
As for what I experienced during my small test I would say that behaviour is rather same. I am attaching graph of CPU usage (5 seconds grid size). It complies what Andrew described. There is certain period of 100% CPU consumption after files are updated physically. Can this be avoided ? I used NetBeans 3.5 beta build #200304222350. To Andrew: I saw that many native speakers use words "CPU consumption" for what you tried to express. Anyway I am not native speaker too ... :-)
Created attachment 10175 [details] Graph of CPU usage during "CVS | Update" command.
Thanks Jiri. So I will keep this issue opened and after we'll port VCS modules into the new projects infrastructure in NB 4.0, I'll look at this problem.
Adding PERFORMANCE keyword. The file status cahcing system will be re-designed to improve stability and performance (issue #32089). This should solve problems of unnecessary refreshing of files. Also the update command should have a better possibility to cooperate with the cache and update the information only when necessary.
Adding dependency on issue #35512. findExistingResource() method should improve the performance of FileObjects refreshing.
3.6 is out, re-scheduling for promotion D (4.0). Adding dependency on issue #35705 rather then issue #35512.
*** Issue 47958 has been marked as a duplicate of this issue. ***
FIXED by cache redesign
I installed the CVS module for VSS and it hangs on the command refresh. It eats up 100% of my CPU. This happened in V4 as well so I upgraded to 5.
Perf team no longer cares about vcscore.