SVN Indexing slow on changesets involving a large number of files

Hi all,

I've just started using Fisheye 3.0.1.

I noticed that SVN repository indexing is slow AND CPU intensive which sounded strange to me, so I did some sampling.

The SVN repository is available via HTTPS which is known to be slow, so I expected bad IO performance but not a steady 100% CPU usage.

I found out that during SVN indexing Fisheye is often executing com.cenqua.fisheye.svn.util.ChangePathUtil.isSubPath(..), which consumes 100% of a CPU.

Typical stack trace:

at java.lang.String.equals(
	at com.cenqua.fisheye.svn.util.ChangePathUtil.isSubPath(
	at com.atlassian.fisheye.svn.Svn2MessageContext.isApplicableChangePath(
	at com.atlassian.fisheye.svn.Svn2MessageContext.getApplicableChangePaths(
	at com.atlassian.fisheye.svn.Svn2MessageContext.isPartOfAdd(
	at com.atlassian.fisheye.svn.Svn2Infill2Processor.getInfo(
	at com.atlassian.fisheye.svn.Svn2Infill2Processor.infillChangeSet(
	at com.atlassian.fisheye.svn.Svn2Infill2Processor.access$100(
	at com.atlassian.fisheye.svn.Svn2Infill2Processor$1.perform(
	at com.atlassian.fisheye.svn.Svn2Infill2Processor$1.perform(
	at com.cenqua.fisheye.cache.BaseRevisionCache.withDbWriteLock(
	at com.atlassian.fisheye.svn.Svn2Infill2Processor.process(
	at com.atlassian.fisheye.svn.Svn2Scanner.slurpRepository(
	at com.atlassian.fisheye.svn.Svn2Scanner.doSlurpTransaction(
	at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(
	at com.cenqua.fisheye.rep.RepositoryEngine.slurp(
	at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(

Is there any fine tuning that I can do via configuration of the repository?

Thanks in advance.

Best regards,


4 answers

Hi Nick,

thanks for your reply. I started indexing from a higher changeset and solved the problem in this way.

BTW, changesets that count 10K files, as an order of magnitude, are still slow but Fisheye processes them without major issues.

The problem with 300k files changesets is that CPU is almost constantly at 100%, suggesting me that com.cenqua.fisheye.svn.util.ChangePathUtil.isSubPath(..) is working on in-memory objects. Also, heap occupation grows and exceeds -Xmx1g settings (no user activity). This makes me suspect that com.cenqua.fisheye.svn.util.ChangePathUtil.isSubPath (or the code block that invokes it) could be further optimized.

Slow indexing because of poor IO is not currently a major concern for me, what's more important IMHO is not having a direct dependency between changeset size and heap occupation.

Thanks again, regards.


I found out that this is happening while processing a huge changeset (300k files).


There are some configurations that can be done to tune your FishEye instance.

They are described here:

Please give it a try. :D

0 vote
Nick Pellow Atlassian Team Jul 01, 2013

Hi Marco - 300k files is indeed a huge changeset.

Has FishEye finished processing this changeset now and your CPU cooled down a little ?

Further, indexing will be much faster for you if you can use svnsync to sync your svn repo local to the fisheye server.



Suggest an answer

Log in or Join to answer
Community showcase
Alexey Matveev
Published Saturday in Jira

How to run Jira in a docker container

Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...

404 views 6 8
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot