We use fisheye with a variety of different svn repositories and generally have good performance. An exception is a recently added, fairly large repository with upwards of 50,000 revisions. Bringing up a diff in a review often takes a long time, sometimes approaching a minute or more. In the admin repository summary we can see blame commands of the form
svn blame -r 0:48585 file:///D:/foo/bar@48585
which given their duration seem to account for the latency. I think use of blame like that can be expected to be pretty time consuming. Are there any configuration options we can use to speed this up? Am I right in thinking the fisheye indexing isn't a factor here? We did set Start Revision to a very recent revision to get the indexing done in reasonable time.
Yes, this is more about how fast the SVN execution is able to take place. I would suggest by using an alternative way which is using the Native Subversion Client instead. It has been proven to improve the speed of SVN execution and it may have worked for you. You can simply test this by downloading it (based on your OS) and then try to execute the command that was stuck like:
time ./svn blame -r 0:48585 file:///D:/foo/bar@48585
and see how long does the execution takes. If its much faster, I would recommand that you migrate over and fully test it on your test server before deploying it onto your production.
Hope that this information helps.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...
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!
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