lock report inefficiencies

When debugging some repository performance problems, I narrowed it
down to repositories with large numbers of locked files. For example,
if I do an "svn ls -v http://server/repo/path" on a repository with
26k locked files, the server generates an 11MB xml response
that included lock information and lock comments for the whole
repository. Almost 100% of this information was discarded in the output
of the "svn ls -v" command.

It appears to be doing a recursive lock report, even though
the "svn ls" command is not requesting recursive behavior.

Is there an API limitation that makes all REPORT commands
for locks show recursive information?

This can make GUIs such as the TortoiseSVN repo-browser painfully
slow due to the large amount of data returned for every path that is
navigated.

Any guidance on where I might start digging into this in
the source code?

Thanks!
Kevin R.
Received on 2010-04-14 19:30:00 CEST