Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

fisheye parsing repository is extremely slow

Crucible/Fisheye(CF) is going to be used for code reviews ONLY even though Fisheye is a SVN Repo browser with limited capabilities compared with ToroiseSVN or RapidSVN. CF needs to parse the repository and then store the results in a SQL based database(MySQL in our case). This is an incredibly slow process. I don't need CF to parse the "actual" source code repository branches (i.e. /main, /trunk, /branches/release[s]/) because the code needs to be inspected before it is allowed on these branches. As a result, the only branch that needs to be parsed is the /branches/private/ subdirectories but this is massive with every designer taking a copy of /main, /trunk or /branches/release[s]/?? to work on. CF with its native/default svn plugin does not understand or emulate the lightweight directory structure of SVN and its incredibly efficient means of copying directories and only storing the deltas.

The actual/entire repository is 5.7G in size and after a day of parsing (and indicating 0% complete) of just the /branches/private/* subtree, the "FISHEYE_INST" directory is 1.2G so this could result in a CF database being considerably larger than the actual SVN repo.


2 answers

1 accepted

0 votes
Answer accepted

I stopped it after 24 hours. I decided to rethink my process and instead created a new /branches/reviews branch and I'll only parse that branch. The process will be that any code submission destine for formal code release (i.e. /main or /branches/releases) will be developed in this new branch. Starting fresh.

I would have be nicer if fisheye could better interface with SVN rather than "indexing" and creating a blotted view in another database.

0 votes
Nick Atlassian Team May 11, 2014

Has the Scan phase already finished ? If so, you can begin using Crucible immediately. The Indexing phase which takes the longest provides functionality needed by FishEye only.

Also - have you added /branches/private/ as an includes to ensure nothing else is indexed by FishEye that doesn't need to be.

Suggest an answer

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

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

188 views 0 5
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