Hi!
I have a newly set-up FishEye/Crucible (2.6.1) running. Indexing of the CVS repositories was a walk in the park.
Now, I also have three ClearCase repositories (which we will migrate to SVN or Perforce later this year).
The initial indexing of the first VOB never completes, it seems.
In the log I see entries like:
2011-07-13 04:27:45,410 DEBUG [InitialPinger1 MedoraNative_CC] fisheye.app ClearCaseRepositoryScanner-processBranch - Finished Branch atlserver_vendor_branch
2011-07-13 04:27:45,410 INFO [InitialPinger1 MedoraNative_CC] perf.timer Timer-output - <- clearcase.processBranch: atlserver_vendor_branch time 33450554023 micros mem_usage = 255340032 heapsize = 461512704 freemem = 206172672
2011-07-13 04:27:45,410 INFO [InitialPinger1 MedoraNative_CC] perf.timer Timer-output - -> clearcase.processBranch: attic mem_usage = 255345264 heapsize = 461512704 freemem = 206167440
2011-07-13 04:27:45,410 DEBUG [InitialPinger1 MedoraNative_CC] fisheye.app ClearCaseRepositoryScanner-processBranch - Starting Branch attic
2011-07-13 04:27:45,410 DEBUG [InitialPinger1 MedoraNative_CC] fisheye.app RepositoryStatus-setMessage - Status change [MedoraNative_CC]: Retrieving change set history for: attic
2011-07-13 04:27:45,410 INFO [InitialPinger1 MedoraNative_CC] perf.timer Timer-output - -> cleartool.execute: desc -fmt %Nd "vob:\RISiClient" mem_usage = 255362120 heapsize = 461512704 freemem = 206150584
2011-07-13 04:27:45,410 DEBUG [InitialPinger1 MedoraNative_CC] fisheye.app ClearCaseContext-executeInteractiveCommand - Executing desc -fmt %Nd "vob:\RISiClient" in: O:\fisheye_native_view
2011-07-13 04:27:45,520 INFO [InitialPinger1 MedoraNative_CC] perf.timer Timer-output - <- cleartool.execute: desc -fmt %Nd "vob:\RISiClient" time 70338 micros mem_usage = 261031968 heapsize = 461512704 freemem = 200480736
If I read this correctly, then it took almost 10 hours, for one branch. So ... two branches a day ... at that speed, the initial indexing will take weeks. What am I missing here? I tried snapshot and dynamic views, no noticable difference. Is that normal?
Sascha
Thanks for raising a support case for this issue. It has now been fixed and will be included in the 2.6.3 release.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Be aware that Atlassian has dropped support for ClearCase/Fisheye !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Forgot to add that the CPU of java.exe during the indexing is at 100%. The cleartool instance used pratically idles.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.