RE: Slow responses, timeouts, FailDBReader, Deadlocks

> I've now asked everyone to do GetLatest 
> through the client instead of the IDE 
> and the transaction logs only reach .5GB.

Noting that Chris Kinsman has already given some
help on the SQL side of things, I'll take yet
another opportunity to talk about the tradeoffs
which are made by choosing to use the IDE client
instead of our standalone client.

We've talked quite a bit about how the IDE client
is slower than our regular client.  A corollary
worth mentioning is that the IDE client can
impose much greater load on the server.

We've been working to make the IDE client as
fast as it can be for our upcoming 2.0 release.
However, it's starting to look like there is very
little improvement left to be made.  Most of the
obvious stuff has already been fixed, and the
basic problem remains:  Visual Studio calls
our client libraries in ways that are very
inefficient.

Boiling it down, the basic issue here is that
Visual Studio makes multiple calls through the
Vault client when it would be better and more
efficient to make just one.

For example, let's say you have a bunch of 
projects in a VS.NET solution.  When you do
a Get Latest for that solution, VS.NET will
do multiple Get Latest calls to the server.
Our standalone Vault client performs the
entire operation in a single call, which is
a lot more efficient.

The same thing applies when checking things
in, to an even greater degree.  If you checkin
a whole bunch of changes in the IDE client,
VS.NET doesn't know how to assemble them all
together into a single transaction like the
standalone client does.  Not only is the
multi-transaction approach much slower, but
it also eliminates the benefit of atomic
checkin transactions.

--
Eric Sink
Software Craftsman
http://software.ericsink.com/

 
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, January 09, 2004 11:48 AM
To: [email protected]
Subject: [vault-list] Slow responses, timeouts, FailDBReader, Deadlocks
Importance: High

We have just under 50 users.  A single server running Vault and SQL Server.
4*700mhz procs, a 3GB database.  120GB hard drive. Win2k. yet we are seeing
very slow responses, timeouts etc.

We all use the IDE Add-in and work in a VSS check-out/check-in style.

We all work in the same Repository.

The symptoms exhibit at the same time as SQL produces 1GB+ transaction logs
per 15 minutes at 'busy' times and the Disk Write Queue Length rockets (up
to 90 sometimes).

I've turned off Reverse DNS and put the DB buffer to the default (768), even
rebooted the server.

I've now asked everyone to do GetLatest through the client instead of the
IDE and the transaction logs only reach .5GB.

Any help would be appreciated.

example log attached:

 <<sgvault.log>> 
Kevin.

-- 

----------------------------------------------------------------------------
--
HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound,
Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are
regulated by the Financial Services Authority.
============================================================================
==