On Tue, Sep 23, 2014 at 9:35 AM, Elias Wulcan <elias.wul...@apptus.com> wrote: > Hello, > > > > I’m trying to figure out why a client is extremely slow fetching subversion > history. Here’s an excerpt from its TCP traffic with the repository. > > > > REPORT /products/ecom/!svn/bc/16411/x/branches/z HTTP/1.1 > > Host: a.b.local > > Authorization: Basic XXXXXXXXX > > User-Agent: SVN/1.8.10 (x64-microsoft-windows) serf/1.3.7 > > Content-Type: text/xml > > Accept-Encoding: gzip > > DAV: http://subversion.tigris.org/xmlns/dav/svn/depth > > DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo > > DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops > > Transfer-Encoding: chunked > > > > 151 > > <S:log-report > xmlns:S="svn:"><S:start-revision>16411</S:start-revision><S:end-revision>1</S:end-revision><S:limit>12</S:limit><S:discover-changed-paths></S:discover-changed-paths><S:include-merged-revisions></S:include-merged-revisions><S:revprop>svn:author</S:revprop><S:revprop>svn:date</S:revprop><S:revprop>svn:log</S:revprop><S:path > > 48 > >></S:path><S:encode-binary-props></S:encode-binary-props></S:log-report> > > 0 > > > > > > Even though there is an S:limit element in the request the repository > responds with what seems like an endless stream of S:log-item elements. Is > the use of S:limit combined with a much larger revision range through > S:start-revision end S:end-revision allowed? Is it something else in the > request that I am missing that causes the limit to be broken? Is the client > misbehaving? Is the server misbehaving? >
What server version? Older server versions do not have support for 'limit'-ed log requests (I think it was introduced in server version 1.5). So if a client talks to an older server, the server will send everything, and the client filters it out on the client side. -- Johan
