Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Crucible\FishEye changing Perforce repo

Simon Hayes April 30, 2014

While evaluating Crucible and FishEye we indexed a subset of our depot. Now we would like to expand it to include the entire depot. I was planning to change the depot path from //depot/something/something/ to //depot/

Just wondering if this will cause a complete re-index or will FishEye\Crucible only index the new data? It took around 2 weeks to index the subset so it would be nice to know what to expect.

Thanks in advance.

1 answer

0 votes
Felipe Kraemer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 30, 2014

Hi Simon,

This action will require a complete re-index, because you'll be reconfiguring the repository location in order to include more folders and files.

In order to have a better idea of how long it would require to have that repository fully indexed again, a suggestion is to configure that repository in a test environment first.

Kind regards,
Felipe Kraemer
Atlassian Support

Simon Hayes May 1, 2014

We're concerned that it will take a month or more to index the data, which is not great. The indexer appeared to be single threaded (ie it only used a single core of the machine it was on), and was CPU bound. Is there any way to speed the process? Are there any plans to improve the performance?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events