Hi,

We have a WSS site with document libraries containing around 40GB of data
right now. We have developped an application that moves files from one
document library to another and have noticed two things.

1) Moving a document using the SharePoint API take from 15-30 seconds
2) tempdb seems to be used heavily on each document move 100% Disk Time with
a queue length of over 2

I see quite a bit of I/O stalls in SQL Server for tempdb which leads me to
think that would be part of the problem. I have a set of disks dedicated to
the content database of that site (6 disk in RAID 1-0) and a disk dedicated
to tempdb.

Anybody has ideas as to what I should be looking for or has experienced a
similar issue?

Thanks,

Re: Moving files and tempdb usage by Engelbert

Engelbert
Tue Mar 28 22:20:22 CST 2006

What's the question ?

Are you asking if there is a way to speed things up ?

As it stands you are describing what you see and what you have and then
asking "Anybody has ideas as to what I should be looking for?" Looking for
what ?

Engelbert

"Mathieu Isabel" <MathieuIsabel@discussions.microsoft.com> wrote in message
news:C1FB44E2-11CE-48EB-B6F8-6409AB7EA5C9@microsoft.com...
> Hi,
>
> We have a WSS site with document libraries containing around 40GB of data
> right now. We have developped an application that moves files from one
> document library to another and have noticed two things.
>
> 1) Moving a document using the SharePoint API take from 15-30 seconds
> 2) tempdb seems to be used heavily on each document move 100% Disk Time
> with
> a queue length of over 2
>
> I see quite a bit of I/O stalls in SQL Server for tempdb which leads me to
> think that would be part of the problem. I have a set of disks dedicated
> to
> the content database of that site (6 disk in RAID 1-0) and a disk
> dedicated
> to tempdb.
>
> Anybody has ideas as to what I should be looking for or has experienced a
> similar issue?
>
> Thanks,
>



RE: Moving files and tempdb usage by MathieuIsabel

MathieuIsabel
Wed Mar 29 06:01:02 CST 2006

Let me make things a bit clearer for everybody:

1) Is it normal that tempdb gets hit that hard when moving files using the
API? Files are about 100KB-500KB each.
2) Has anybody reached better performance while moving files programmatically?

Some clarification, I'm not moving the files via WebDAV because I've had
problems in the past where the WebClient would die on me an crash the whole
RPC server, hence preventing some SharePoint functionnality and remote
administration. I also have to copy some of the attributes from one library
to another.

I hope this is a bit clearer now.

Thank you,



"Mathieu Isabel" wrote:

> Hi,
>
> We have a WSS site with document libraries containing around 40GB of data
> right now. We have developped an application that moves files from one
> document library to another and have noticed two things.
>
> 1) Moving a document using the SharePoint API take from 15-30 seconds
> 2) tempdb seems to be used heavily on each document move 100% Disk Time with
> a queue length of over 2
>
> I see quite a bit of I/O stalls in SQL Server for tempdb which leads me to
> think that would be part of the problem. I have a set of disks dedicated to
> the content database of that site (6 disk in RAID 1-0) and a disk dedicated
> to tempdb.
>
> Anybody has ideas as to what I should be looking for or has experienced a
> similar issue?
>
> Thanks,
>