Index sizes in Crucible’s “light” Fisheye vs full Fisheye for Perforce repositories with many branches and cross integrations

[Fesifaz Ino]

I’m trying to use Crucible with my Perforce repository. Originally, I tried to use Crucible and Fisheye together, but I wasn’t able to get my repository fully indexed with Fisheye. The problem was that we have many, many branches and many, many cross-integrations between those branches. Fisheye’s index ended up being too big for my largest machines.

I don’t care about having all of the features of full Fisheye. I’m really only interested in Crucible. So I could try using Crucible without Fisheye, and use Crucible’s native repository access and light Fisheye. But that’s only going to work if light Fisheye indexes less stuff than full Fisheye. Will the light Fisheye index be smaller than the full Fisheye index?

(If you’re wondering if I tried using the lightSCM plugins, which don’t create any indexes, see the other question I posted. https://answers.atlassian.com/questions/151782/viewing-diffs-when-using-perforce-p4-lightscm-in-crucible-without-fisheye )

[Sergey Svishchev]

Only Crucible dev team really knows the answer -- documentation is unclear: https://confluence.atlassian.com/x/VAjSEQ