[cvsnt] Extremely slow remote CVSNT access

[Joost van der Plas]

Thanks for the golden tip, Bo!

Indeed it must be DNS-related. In my case, I don't use DNS within my LAN,
only when accessing the Internet (the DNS of my ISP). My LAN is connected
via a dial-up router and ISDN to the internet. After some testing it is now
clear: when the router link is open the response time is 2-4 seconds,
otherwise 20 seconds. So even with absent DNS the host names ARE resolved,
although slow. Apparently the process waits for the DNS round-trip to
time-out.

I could bring up the DNS on my local NT Server but why. Can I also resolve
host names via the local etc/hosts file or WINS? OK, I'm going to try this
myself...

Thanks again!

Joost

"Bo Berglund" <Bo.Berglund at system3r.se> wrote in message
news:mailman.630.1064314180.630.cvsnt at cvsnt.org...
Look at the DNS settings on your LAN (on both machines).
You need proper name lookup to get fast reponses.

/Bo

-----Original Message-----
From: Joost van der Plas [mailto:joost.cvsnt at musigma.nl]
Sent: den 23 september 2003 11:37
To: cvsnt at cvsnt.org
Subject: [cvsnt] Extremely slow remote CVSNT access


A fresh install of CVSNT  2.0.9 on a 800MHz Win2000 notebook. The repository
root and temp are on a local NTFS partition. Only a small TEST repository
(20 files)
Trying to access this from remote Win NT4 machines on the LAN (400MHz,
256MB), using :sspi: protocol.
Response is extremely slow! 20 seconds for a simple "cvs ls" command. While
waiting I monitor the task manager on the server and  the client and keep an
eye on the LAN switch (100Mb ethernet): no CPU load, no harddisk thrashing,
not out of memory,  no LAN traffic. If I keep repeating the ls command
SOMEtimes the response comes within 4 seconds, but most of the  time 16-20
seconds.
On the local machine, using sspi protocol the response is almost
instantaneous.

I had similar problems last week when I installed the CVSNT 2.1.1 beta on my
NT4 Server:  also 20 second delays there (in that case also when using sspi
on the local machine) and I blamed it on the beta or on the slow CPU (that
server is a 166MHz pentium). So I decided to install the stable release, and
on a faster machine. But no go.

Any ideas?

Joost


_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt