We are using 2.0.3 both GUI client & server.
I've been trying to add large projects to Vault (they're refugees from our VSS database, but I got scared off using the VSS import tool). By large, I mean 25-80 MB of source code and other files.
What we are experiencing is that the GUI client adds all the files, then sits there for an eternity while committing the transaction, with the prompt "Ending transaction..." CPU on the Vault server and SQL server is minimal (~4%). Our DBA took a look and found two transactions originated by Vault:
sp_who2 active
dbcc inputbuffer (53)
dbcc inputbuffer (55)
RPC Event 0 dbo.spaddfile;1
RPC Event 0 dbo.spgetuserrepositorylastchange;1
It says in Query Analyzer that the second transaction is blocking the first.
After a long time (up to an hour), eventually it commits and all is OK.
During the commit activity, no one else is able to use Vault - it just hangs on them.
Adding large projects slow, hangs Vault
Moderator: SourceGear
Oh, sorry about that. I thought you were reporting the situation.
Yes, this is the behavior of Vault 2.0.3. During long, long transactions, such as adding thousands and thousands of files in one transaction, there are locking issues within the database which may block other users until the transaction is complete.
Fixes here will not be trivial, but we have them logged to be addressed in an upcoming release of Vault.
Until then, it would be best to break large transactions into smaller sub-transactions whenever possible.
Yes, this is the behavior of Vault 2.0.3. During long, long transactions, such as adding thousands and thousands of files in one transaction, there are locking issues within the database which may block other users until the transaction is complete.
Fixes here will not be trivial, but we have them logged to be addressed in an upcoming release of Vault.
Until then, it would be best to break large transactions into smaller sub-transactions whenever possible.
Jeff Clausius
SourceGear
SourceGear