On 4/16/12 5:54 PM, John B. Matthews wrote:
In article<LpYir.88442$s82.47213@newsfe10.iad>,
Daniel Pitts<newsgroup.nospam@virtualinfinity.net> wrote:
On 4/15/12 10:51 PM, John B. Matthews wrote:
In article<HIHir.9015$YM2.6283@newsfe05.iad>,
Daniel Pitts<newsgroup.nospam@virtualinfinity.net> wrote:
Well, I did find one way to speed things up. An "info" request
of the file on the tag is relatively fast, and includes the
"last change revision" of that file. I can then do a log of
that file on the trunk (Which is faster by magnitudes), and
anything after that revision can be considered a change after
that file was originally tagged.
Anyway, I'm still open to any other advice on the matter.
This reminds me of a project that had a particularly tangled
per-directory access control configuration. You might look at
the speed versus security tradeoff in "Disabling path-based
checks."
I'm not sure I understand what you mean by that, but that does
remind me that our admins have prevented checkouts that don't
have "/branches/*/", "/tags/*/" or "/trunk/" in them. Not sure if
that is contributing to the problem or not.
I'm not sure how they're enforcing it, but "Per-directory access
control" is one way, and "Disabling path-based checks" is one
alternative, both discussed here:
<http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir>
A symptom is that the time required to obtain older `info`
increases (roughly) geometrically with age.
That actually seems to be a likely cause. I'm going to ask our admins to