The request for svn revision suddenly seems slow (so how can svn 1.5 be?)

Question

Shortly after upgrading our repository to Subversion 1.5, my team switched to writing a new application for several months, and then suddenly returned to the original code base. Our developers use TortoiseSVN 1.5.9 and Subversion Client 1.6 (only svnversion -n) and Subversion 1.5 on our server. Our clients connect via svn + ssh.

Our source codebase combines the SVN version number into code using svnversion -nto query the current WC version. Suddenly, however, this operation went over to what I recall, taking a short second or two until 10 seconds (and I saw even worse in the VM development environment, etc.). We also experienced similar delays returning and experimenting with Tortoise SubWCRev and Subversion Client 1.5.

This is not a serious problem, but it is certainly annoying, because this check is performed as a preliminary compiler before each build operation. So I would like these few seconds to leave our feedback loop!

So my question is: Have I been out of my old codebase for too long, or did someone else notice a delay for this operation?

If this delay is a new phenomenon, someone has fixed it. If so, how?

Answer 1

The recommended red-bean svn book says that large commits (many files in one commit) can greatly affect performance. Have you recently checked a large number of files, say, in the last 100 checks?

Answer 2

. Apache (http (s)), svn log. . . . :

, svn log. . [...] , , . : , mod_authz_svn, mod_dav_svn - Apache httpd .

Answer 3

​​ . auth? , HTTP-. - . auth, . back-end, . IMAP ( mod_auth_imap). auth ( - / ), : 1,5 .

Answer 4

( ) zsh svn:

sed -ns "4 p" **/.svn/entries | sort | uniq

It will provide you with an update of your last update or a list of changes if your repository is mixed. This is not as complete as what svnversion does, and may not be compatible with all versions of svn (mine is 1.6.16), but it does work in some cases, and it is incredibly fast (1s versus 3mn in my case! )