It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Any way to increase Fisheye indexing on large Subversion operations?

Frequently, we copy our entire trunk as a branch. This is a lot of data, and takes Fisheye a long time to index this. While this is being indexed, other users are committing smaller changes that would not take Fisheye too long, but Fisheye is still stuck on the large branch creation. This causes a problem for us because we use Crucible to review, and Crucible cannot see those smaller changes because Fisheye is still indexing the large branch creation. Is there any way for those smaller changes to be seen and reviewed even if Fisheye is still working on the branch?

5 answers

1 accepted

0 votes
Answer accepted
Lukasz Pater Atlassian Team Aug 04, 2013

In general FishEye needs to scan the revisions in order they're created, so it needs to finish the branch creation before it gets to the newer commits.

If your reviews are mostly on trunk, you might consider creating a separate repository that just indexes trunk (or the relevant branches), and use that for reviews.

If you're experiencing excessively long indexing times on branch creation, try raising a support request on https://support.atlassian.com.

By default, FishEye uses one thread to process the incremental changes.
You can increase the number of Incremental Index Threads to 2.
One thread will then be busy processing the large commit, but it's no longer blocking, as the other thread will visit your other repositories to see if there are any commits in them.

See also https://confluence.atlassian.com/display/FISHEYE/Configuring+indexing .

I have threads set to the default which I believe is 3.

The default (i.e. if you haven't filled in any value) is 1.

Lukasz Pater Atlassian Team Aug 04, 2013

3.0.0 increased the default numer of initial and indexing threads to 3 (FECRU-3329).

Are you running Fisheye 3?

Fisheye 3.0.1

FE3 speeds up svn indexing but it's still linear. But you should check if symbolic rules setup matches your actual repository layout.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

We want to hear from you! How do you use Slack and Atlassian together?

Hi Everyone! My name is Mina and I am on Atlassian’s Ecosystems Marketing team. Our team is focused on our technology partnerships and marketplace apps. One of Atlassian’s partners is Slack, who ...

73 views 0 4
Join discussion

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you