file is too large to show diff

Crucible File Diff function gives an error comparing revisions of a svn file (2.6Mb):

"(Filename) is too large to show a diff"

Is the default max filesize a configurable setting? If so, where is that value set?


2 answers

1 accepted

5 votes
Accepted answer

If you use Subversion you can adjust the size of what files are diff'ed by setting the Fisheye Maximum Indexable File Size to something smaller than the default 5mb.  The setting notes that "in Subversion repositories, files larger than this size will not have their contents or diffs displayed in the Fisheye or Crucible user interface...".  However, changing the default won't back-fill existing data, you have to reindex. 

Administration | Repository Settings | Defaults | Other Settings.  See:

That said, Crucible may have some other built-in limit limitation on allowable file/diff size for reviews, but if it does it's not a configurable setting I've ever found. 

The instructions say "files larger than this size will not have their contents or diffs displayed".  Are we supposed to make this parameter smaller to make it work?

Not sure I understand the question.  By default, Fisheye will only index files that are 5mb or smaller, and it skips anything larger than that.  So indexing works, it just works selectively. 

If you want text files larger than that to be indexed so you can view/search/diff them, you'll need to set it to a larger value (i.e. 10mb).  You don't want to set it too high, or you will adversely affect performance/resource usage.

If you set it to smaller than 5mb, fewer files will be indexed.  Presumably if you set it to 0mb, no files will be indexed. 

Thanks for the good information, that's exactly what I needed. We'll run a reindex off-hours this weekend.

If it works for you, please mark answer accepted. Just curious - why did you lower Max Indexable File Size? We've had performance issues, but I haven't seen this as a suggested tuning anywhere.

When we first installed Fisheye/Crucible several months ago, we had trouble indexing some large svn repositories, and thought reducing this might help. I suspect it had little effect, but our repositories are now stable so it won't be an issue.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 13, 2019 in Jira Service Desk

What's new in Jira Service Desk Server: Introducing 4.0 & more - Feb 2019

Hello Atlassian Community!  I'm Teresa, the Product Marketing Manager   for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...

107 views 0 0
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