[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: Edward Ned Harvey <svn_at_nedharvey.com>
Date: Fri, 2 Jul 2010 12:08:37 -0400

> From: Stefan Sperling [mailto:stsp_at_elego.de]
>
> 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.

Yes! This worked, only it's the first time I've ever used gprof, and I'm
not sure I'm using it right, and I'm not sure what I should post here ...

First, I just did "svn cleanup" which completed instantly, and generated the
gmon.out file. I then tried gprof gmon.out, and it says "not in a.out
format"

So then I consulted the man page, and I think I'm supposed to give it both
the svn and gmon.out files right? So
gprof `which svn` gmon.out

And it spits out a bunch of info.

So then I repeated the above process, using one of the problem scenarios. A
commit which takes 15 minutes and should take 11 mins. (For some reason,
this time it only took 8 min.) But as I read the output, I see numbers like
"40" calls to something ... which don't sound like 8 mins worth of
processing.

So I'm not sure I did this right.

The output was:

Flat profile:

Each sample counts as 0.01 seconds.
 no time accumulated

  % cumulative self self total
 time seconds seconds calls Ts/call Ts/call name
  0.00 0.00 0.00 42 0.00 0.00 data_start
  0.00 0.00 0.00 1 0.00 0.00
svn_cl__args_to_target_array_print_reserved
  0.00 0.00 0.00 1 0.00 0.00
svn_cl__cleanup_log_msg
  0.00 0.00 0.00 1 0.00 0.00 svn_cl__commit
  0.00 0.00 0.00 1 0.00 0.00
svn_cl__conflict_baton_make
  0.00 0.00 0.00 1 0.00 0.00 svn_cl__get_notifier
  0.00 0.00 0.00 1 0.00 0.00
svn_cl__make_log_msg_baton
  0.00 0.00 0.00 1 0.00 0.00
svn_cl__print_commit_info
  0.00 0.00 0.00 1 0.00 0.00
truncate_buffer_at_prefix

 % the percentage of the total running time of the
time program used by this function.

cumulative a running sum of the number of seconds accounted
 seconds for by this function and those listed above it.

 self the number of seconds accounted for by this
seconds function alone. This is the major sort for this
           listing.

calls the number of times this function was invoked, if
           this function is profiled, else blank.
 
 self the average number of milliseconds spent in this
ms/call function per call, if this function is profiled,
           else blank.

 total the average number of milliseconds spent in this
ms/call function and its descendents per call, if this
           function is profiled, else blank.

name the name of the function. This is the minor sort
           for this listing. The index shows the location of
           the function in the gprof listing. If the index is
           in parenthesis it shows where it would appear in
           the gprof listing if it were to be printed.

                     Call graph (explanation follows)

granularity: each sample hit covers 2 byte(s) no time propagated

index % time self children called name
                0.00 0.00 1/42 svn_cl__print_commit_info
[8]
                0.00 0.00 1/42 svn_cl__make_log_msg_baton
[7]
                0.00 0.00 1/42
svn_cl__args_to_target_array_print_reserved [2]
                0.00 0.00 5/42 svn_cl__commit [4]
                0.00 0.00 9/42 notify [24]
                0.00 0.00 11/42 svn_cl__get_log_message
[57]
                0.00 0.00 14/42 main [23]
[1] 0.0 0.00 0.00 42 data_start [1]
-----------------------------------------------
                0.00 0.00 1/1 svn_cl__commit [4]
[2] 0.0 0.00 0.00 1
svn_cl__args_to_target_array_print_reserved [2]
                0.00 0.00 1/42 data_start [1]
-----------------------------------------------
                0.00 0.00 1/1 svn_cl__commit [4]
[3] 0.0 0.00 0.00 1 svn_cl__cleanup_log_msg [3]
-----------------------------------------------
                0.00 0.00 1/1 main [23]
[4] 0.0 0.00 0.00 1 svn_cl__commit [4]
                0.00 0.00 5/42 data_start [1]
                0.00 0.00 1/1
svn_cl__args_to_target_array_print_reserved [2]
                0.00 0.00 1/1 svn_cl__make_log_msg_baton
[7]
                0.00 0.00 1/1 svn_cl__cleanup_log_msg [3]
                0.00 0.00 1/1 svn_cl__get_notifier [6]
                0.00 0.00 1/1 svn_cl__print_commit_info
[8]
-----------------------------------------------
                0.00 0.00 1/1 main [23]
[5] 0.0 0.00 0.00 1 svn_cl__conflict_baton_make [5]
-----------------------------------------------
                0.00 0.00 1/1 svn_cl__commit [4]
[6] 0.0 0.00 0.00 1 svn_cl__get_notifier [6]
-----------------------------------------------
                0.00 0.00 1/1 svn_cl__commit [4]
[7] 0.0 0.00 0.00 1 svn_cl__make_log_msg_baton [7]
                0.00 0.00 1/42 data_start [1]
-----------------------------------------------
                0.00 0.00 1/1 svn_cl__commit [4]
[8] 0.0 0.00 0.00 1 svn_cl__print_commit_info [8]
                0.00 0.00 1/42 data_start [1]
-----------------------------------------------
                0.00 0.00 1/1 svn_cl__get_log_message
[57]
[9] 0.0 0.00 0.00 1 truncate_buffer_at_prefix [9]
-----------------------------------------------

 This table describes the call tree of the program, and was sorted by
 the total amount of time spent in each function and its children.

 Each entry in this table consists of several lines. The line with the
 index number at the left hand margin lists the current function.
 The lines above it list the functions that called this function,
 and the lines below it list the functions this one called.
 This line lists:
     index A unique number given to each element of the table.
                Index numbers are sorted numerically.
                The index number is printed next to every function name so
                it is easier to look up where the function in the table.

     % time This is the percentage of the `total' time that was spent
                in this function and its children. Note that due to
                different viewpoints, functions excluded by options, etc,
                these numbers will NOT add up to 100%.

     self This is the total amount of time spent in this function.

     children This is the total amount of time propagated into this
                function by its children.

     called This is the number of times the function was called.
                If the function called itself recursively, the number
                only includes non-recursive calls, and is followed by
                a `+' and the number of recursive calls.

     name The name of the current function. The index number is
                printed after it. If the function is a member of a
                cycle, the cycle number is printed between the
                function's name and the index number.

 For the function's parents, the fields have the following meanings:

     self This is the amount of time that was propagated directly
                from the function into this parent.

     children This is the amount of time that was propagated from
                the function's children into this parent.

     called This is the number of times this parent called the
                function `/' the total number of times the function
                was called. Recursive calls to the function are not
                included in the number after the `/'.

     name This is the name of the parent. The parent's index
                number is printed after it. If the parent is a
                member of a cycle, the cycle number is printed between
                the name and the index number.

 If the parents of the function cannot be determined, the word
 `<spontaneous>' is printed in the `name' field, and all the other
 fields are blank.

 For the function's children, the fields have the following meanings:

     self This is the amount of time that was propagated directly
                from the child into the function.

     children This is the amount of time that was propagated from the
                child's children to the function.

     called This is the number of times the function called
                this child `/' the total number of times the child
                was called. Recursive calls by the child are not
                listed in the number after the `/'.

     name This is the name of the child. The child's index
                number is printed after it. If the child is a
                member of a cycle, the cycle number is printed
                between the name and the index number.

 If there are any cycles (circles) in the call graph, there is an
 entry for the cycle-as-a-whole. This entry shows who called the
 cycle (as parents) and the members of the cycle (as children.)
 The `+' recursive calls entry shows the number of function calls that
 were internal to the cycle, and the calls entry for each member shows,
 for that member, how many times it was called from other members of
 the cycle.

Index by function name

   [1] data_start [4] svn_cl__commit [7]
svn_cl__make_log_msg_baton
   [2] svn_cl__args_to_target_array_print_reserved [5]
svn_cl__conflict_baton_make [8] svn_cl__print_commit_info
   [3] svn_cl__cleanup_log_msg [6] svn_cl__get_notifier [9]
truncate_buffer_at_prefix (util.c)
Received on 2010-07-02 18:09:26 CEST

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