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

'update' question

From: Nicklas Norling <nicklas.norling_at_ifsab.se>
Date: 2004-05-07 13:48:39 CEST

I have a developer sitting on a pretty bad remote line with 500+ms network
He's getting the "updates" fast, but then it "just sits around doing nothing
for like
30 minutes". I asked him to clock it and he had to wait 30 minutes for an
update with
virtually no code coming out.
He's running the latest version of TSVN towards a subversion 1.0.2 server on
using the http access protocol. He's got a modern 7200 RPM HD.
I'm able to do exactly as him, but locally. The clock stopped at 38 seconds
with no code
checked out. My hardware are about the same as his.
However, when code are checked out, even locally, I have noticed that the
update "stops"
after the files have been transmitted. There appears to be high disk
activity for awhile until
it finishes. I'm seeing the same behavior with svn.exe.
What we're concerned with is that there might be some network activity
involved in this
"silent" period and that it's doing network "ping-pong" and hence might be
things down unnecessarily?
Can anyone enlighten us? Maybe this is already old news?
Received on Fri May 7 13:49:13 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.