[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: xdelta, svndiff, zlib, or some other problem

From: Branko Čibej <brane_at_xbc.nu>
Date: Mon, 05 Jul 2010 07:00:45 +0200

On 02.07.2010 14:14, Daniel Shahaf wrote:
> Edward Ned Harvey wrote on Fri, 2 Jul 2010 at 07:42 -0400:
>
>> We first experienced the problem in production. Clients connecting via
>> svn:// to svnserver.
>>
>> Since I'm debugging, I'm able to reproduce it on the command line with svn,
>> using svn:// so there is no server.
>>
>>
> Okay.
>

Um, not OK? Either there's a typo in the quoted text above and you're
actually testing with a file:// URL, or you're indeed testing with a
svn:// URL, which explains why you only get a client trace from gprof --
you're not actually profiling the server which is where the problem most
likely lies.

In some other post you mentioned that you got a whole lot of hanler
calls in svn_txdelta_send_txstream(); let me guess, one per 100k of file
data.

I'd also suggest you try a static build, i.e., by passing
--disable-shared --enable-static and CFLAGS=-pg to configure. That
should generate a statically-linked svn binary (except for non-svn
libraries), then make sure you create a new repository and use a file://
URL to test your data set. If gprof/oprofile still doesn't trace into
the libraries, then it's time to begin the head-scratching. :)

It's quite unlikely in my experience that you'll find the cause of this
kind of problem without a good runtime profile in hand.

-- Brane
Received on 2010-07-05 07:02:27 CEST

This is an archived mail posted to the Subversion Dev mailing list.