RE: Connection Delay?

 
Monte,

Jeremy just came into my office and told
me what is probably going on.  I'm annoyed with 
myself for not realizing this on my own.

Like another poster said, ASP.NET is automatically
recycled on a regular interval.  However, the
problem is not the time spent recompiling in
the .NET JIT.  Rather, the delay is probably
due to the Vault server rebuilding its RAM cache.

This is one of those items which is linear in
your total tree size.  Do you have a large
repository?  How many files?

For most people with a smaller tree, this rebuild
of the cache is hardly noticeable at all.

This potential explanation of your problem seems
to fit the facts, although I would not expect the
delay to be as long as 10 minutes.

--
Eric Sink
Software Craftsman
http://software.ericsink.com/
 
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Monte Kalisch
Sent: Friday, December 19, 2003 9:36 AM
To: [email protected]
Subject: [vault-list] Connection Delay?

We upgraded to Vault 1.2.3 this week (though we still have a couple of
clients using 1.2.2), and every morning when the first person tries to
connect, there is a SIGNIFICANT delay (upwards of 10 minutes).  We've
tried rebooting the server; that hasn't changed anything.  After the
first person gets connected, though, it seems to run really fast for
everyone.

Any ideas?

Monte Kalisch
Director of Product Development
Connections Academy
_______________________________________________
vault-list mailing list
[email protected]
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list