Crucible Indexing is very slow and Stuck

I have initiated the indexing of data and its very slow and stuck at svn diff command.

I know the revisions and branches i want to avoid and should not be considered for indexing therefore i have exclusions in place. Its seem below command is standard procedure Crucible is following to grab the changes or difference.

svn diff --summarize -r 90907:90908 file:///D:/SubversionMirrors/Repos/Directory@90908

These particular revision and some other include more than million transaction or changes and taking very long time because of which indexing has not completed yet and review requests don't have proper data.

I tried below option to resolve this:

  1. Configured exclusions
  2. Configured Symbolic rules
  3. Increased subversion timeout period to 1 day
  4. Tried fixing resource utilization to 1 and 3

Can anyone suggest me any option which can avoid svn diff command on the revision having million changes?


How can i make my indexing faster and other issue i am in right now is indexing never completes but always show 99.9% completed. 

Can anyone please help?


2 answers

1 accepted

0 votes
Answer accepted

Hi Taha,

I used "time ./jsvn diff --summarize" feature in FISHEYE_INSTANCE/lib/svn/jsvn to know the time it would take to complete the command. As per result it should have finished the process in 1hr and 3 minutes but to my surprise it is not.

I know the similar revision which have milion changes and will take time not sure how much. I want to avoid those revision as the operation performed on those revisions was svn move to archive outdated old branches.

If there is anyway to avoid this command on those revision that would help to resolve the problem. 

Thanks for suggestion




You can tell Fisheye to Start Indexing from a particular revision but unfortunately you can't tell it to skip a particular revision. There is feature request with atlassian for this - I agree if we have feature to skip revision then it would be very handy in these case. We also faced this kind of issue in the past but only way to get around is to increase the time out and wait for these revision to complete. What Atlassian suggested to improve performance is to use *Native Subversion Client* but haven't tried since it may increase memory usage during reindexing. You can check this document for more info

Thanks i think you are right wait is good way to move ahead.

Hi Balbir,

Firstly try to run this command on you Subversion Server itself and note down the timing

svn diff --summarize -r 90907:90908 file:///D:/SubversionMirrors/Repos/Directory@90908

Then try to increase subversion timeout, it can be more than 1 day as well.




Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Jira

Updates to give you visibility into what's coming in Jira Server and Data Center

Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...

407 views 1 13
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you