I'm no pro, so I don't know how the correct debug approach would be for this
case.
I did a strace on the proccess and saw that it started hanging when waiting
for input from the stream.
Here's the corresponding part of the strace output:
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
connect(4, {sa_family=AF_INET, sin_port=htons(10023), sin_addr=inet_addr("
78.46.66.102")}, 16) = 0
read(4, "( success ( 1 2 ( ANONYMOUS ) ( "..., 4096) = 76
write(4, "( 2 ( edit-pipeline svndiff1 abs"..., 100) = 100
read(4, "( success ( ( CRAM-MD5 ) 14:as3s"..., 4096) = 47
write(4, "( CRAM-MD5 ( ) ) ", 17) = 17
read(4,
Then nothing would happen for a while.
After the usual 5 - 8 minutes, it continued.
2008/4/28 Karl Fogel <kfogel_at_red-bean.com>:
> "Thorsten Schmitt-Rink" <schmittrink_at_gmail.com> writes:
> > thank you for the fast reply.
> > Yes the externals are running on the same server, in the same repository
> root
> > as the other repositories.
> > When I directly checkout one of the externals, the performance is great.
> > As soon as I check out the main repository, the proccess hangs for about
> 8
> > minutes each time it reaches an external.
> > The repositories are all really small and don't contain big files.
> > I hope I didn't miss to provide important data.
> >
> > P.S.:
> > A colleague just reported, he is experiencing the same issue on svn via
> apache.
>
> Something is *definitely* wrong with 8 minutes.
>
> Can you debug into the client and figure out where it's spending that
> time? Is it delaying on some request?
>
Received on 2008-04-28 22:14:48 CEST