Ending the Transaction

Whittey · Post by **Whittey** » Fri Apr 02, 2004 10:05 am

Are there any performance adjustments that can be made to speed up the Ending? Vault Server and Client v1.2.1.737.

[4/2/2004 10:46:07 AM] Preparing data to begin transaction
[4/2/2004 10:46:08 AM] Beginning transaction
[4/2/2004 10:46:** AM] Check in (a bunch of files totaling maybe 2mb)
[4/2/2004 10:46:44 AM] Ending the transaction
[4/2/2004 10:48:20 AM] Transaction completed successfully

-=Whittey=-

sterwill · Post by **sterwill** » Fri Apr 02, 2004 2:05 pm

All the work that happens between "Ending Transaction" and "Transaction completed successfully" is server work, and will happen faster as SQL Server runs faster. I think the largest factor for processing checkins would be disk speed, although the server may slow down if it's low on memory and modifying a large tree structure. Can you describe your server hardware configuration (disk speed, whether RAID, memory, CPU, other load)?

Whittey · Post by **Whittey** » Fri Apr 02, 2004 3:08 pm

The machine definately isn't a powerhouse, but I figure it shouldn't be so bad.

PIII 600
256mb ECC PC100
OS Drive is 2x10k SCSI RAID1 (HP NetRAID0
Data Drive is 2x7200rpm 200gig IDE RAID1 (Adaptec 2400)
OS is Windows 2003 Std

Machine does nothing else but Vault.

-----------------------------------------------------------------------------

I just checked in some stuff, here is the play:

Using my PC clock I recorded:
3:55:15 Connect
3:55:48 Retreiving Repository
3:56:44 Saving
3:56:05 Ready

So now i'm all logged in. I'm the only person using it at this time across a 100mbit switched network.

I hit Check In and click OK(I have Keep Checked Out checked). Here are my messages:

[4/2/2004 3:57:25 PM] Preparing data to begin transaction
[4/2/2004 3:57:25 PM] Beginning transaction
[4/2/2004 3:57:26 PM] Check in $/Databases/Waterford/Externals/harbour.flt
[4/2/2004 3:57:28 PM] Ending the transaction
[4/2/2004 3:57:37 PM] Transaction completed successfully

The harbour.flt file is 803KB, binary.

-=Whittey=-

sterwill · Post by **sterwill** » Fri Apr 02, 2004 4:31 pm

That seems pretty slow. Our in-house Vault server is similar in hardware configuration to yours, and our performance is much better. Do you regularly run SQL Server database maintenance jobs?

Post by **jeremy_sg** » Fri Apr 02, 2004 5:02 pm

One thing that impacted the performance in 1.2, but was fixed for 2.0 was the characteristics of all the parent folders. If in your example, $/Databases/Waterford/ had 500 files and folders, the saving of the repository would take a long time, so every transaction below it would be affected. In general, several performance improvements came with 2.0. You should consider upgrading.

Whittey · Post by **Whittey** » Mon Apr 05, 2004 6:35 am

I will be upgrading soon. The $/Databases has about 30 directories and each of those has 500+ files and are typically over 200mb each. Would upgrading also help out the initial connection time?

-=Whittey=-

Post by **jeremy_sg** » Mon Apr 05, 2004 7:16 am

That does sound like it would be helped by the 2.0 fix. I can't think of anything specific in 2.0 related to startup time, but there were lots of improvements that made it in to 2.0.

Whittey · Post by **Whittey** » Mon Apr 05, 2004 7:32 am

Just did a checkin of that entire directory.

[4/5/2004 8:53:02 AM] Preparing data to begin transaction
[4/5/2004 8:53:18 AM] Beginning transaction
**********
[4/5/2004 8:58:43 AM] Ending the transaction
[4/5/2004 9:15:50 AM] Transaction completed successfully

210mb and 500+ files

Seems i'll have to get that upgrade scheduled real soon.

-=Whittey=-

Whittey · Post by **Whittey** » Tue Apr 20, 2004 9:22 am

***** ADD FILES *****
[4/20/2004 11:04:19 AM] Preparing data to begin transaction
[4/20/2004 11:04:21 AM] Beginning transaction
[4/20/2004 11:**:** AM] Add 125.81 MB, 459 Files, 15 Folders
[4/20/2004 11:07:05 AM] Ending the transaction
[4/20/2004 11:09:07 AM] Transaction completed successfully

***** Check In *****
[4/20/2004 11:16:28 AM] Preparing data to begin transaction
[4/20/2004 11:16:28 AM] Beginning transaction
[4/20/2004 11:16:29 AM] Check in about 30 files, can't be more than 10mb.
[4/20/2004 11:16:39 AM] Ending the transaction
[4/20/2004 11:17:08 AM] Transaction completed successfully

It still takes longer to end the transaction than to do the actual transaction. This is now upgraded to 2.0.1.2137. I am ordering 512mb more for that machine, hoping that will help.

-=Whittey=-

Post by **jeremy_sg** » Tue Apr 20, 2004 9:53 am

Understand that ending the transaction is where the actual work of inserting data into SQL happens. Ending will almost always take the longest.

sterwill · Post by **sterwill** » Tue Apr 20, 2004 9:54 am

"Ending transaction" is when all the new data is checked for consistency by the server and merged into the database. All of the server-intensive work is done after the "Ending transaction" message is displayed by the client. The previous work is just uploads and network traffic.