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

On Fri, Jul 02, 2010 at 10:07:00AM +0300, Daniel Shahaf wrote:
> Edward Ned Harvey wrote on Thu, 1 Jul 2010 at 23:13 -0400:
> > I went into subversion/svn, and I edited every single .c file. I put
> > a fprintf(stderr,"function name\n"); into every function, just to show
> > me where svn is going after it's initiated.
>
> By hand!? I thought they had a rule in Programming School against doing
> repetitive tasks by hand like that. :-)
>
> 'gcc -pg' does this. And most likely there are other tools too.

Yes. Re-compile all of svn with -pg in CFLAGS. Something like:

        env CFLAGS="-O0 -g -pg" ./configure --enable-maintainer-mode \
                --prefix=/usr/local/svn/
        make && make install

Then use a profiler such as gprof to profile runs of svn using
a file:/// URL to access the repository (if you don't use file://,
make sure to profile both the server and the client).

See the gprof man page for details on the profiler.

Simply posting the profiler output for one of the problematic
runs here, so many people can take a look at it, will most likely
uncover the root of the problem.

Stefan
Received on 2010-07-02 13:39:42 CEST