Windows Performance Analysis help

[KeithK]

I am realatively new to using perfmon and have been tasked with determining
the cause and solution to a problem with the time it takes to perform a
scheduled task that copies data from one server to another. The time to copy
(using XCopy) has nearly doubled overnight.

My plan is the following:

1) 15 min prior to the copy time, begin running perfmon on the following
counters:
Processor : % Processor Time
Memory : Pages/sec
Paging File : % Usage
Physical Disk : % Disk Time
Network Interface: Bytes Total/sec
2) 15 min past copy time stop running perfmon.
3) Import into PAL (Performance Analysis of Logs) for review and to try to
determine cause/bottleneck of the copy process in order to make a
recommendation.

I would appreciate any additional suggestions on how I should go about this,
any counters I should add, what I should I be focusing on in my analysis, or
any good artciles/books on the subject etc...

Thanks in advance!
Keith

 

[Mathieu CHATEAU]

Re: Windows Performance Analysis help

Hello,

depending the number and size of files to copy, robocopy may behave better.
you will find it in the 2003 resrouce kit:
http://www.microsoft.com/downloads/...69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

Robocopy can copy only missing or changed files to save time if possible

Check also for :
-networks error (on the switch and server)
-Be sure they are in gigabit or at least 100M/full duplex on both side
(servers and switch port)

Shutting down the antivirus client would help too.

--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr

"KeithK" <KeithK@discussions.microsoft.com> a écrit dans le message de
news:C2DEE073-E6B2-4E39-84BA-81CE99930919@microsoft.com...
>I am realatively new to using perfmon and have been tasked with determining
> the cause and solution to a problem with the time it takes to perform a
> scheduled task that copies data from one server to another. The time to
> copy
> (using XCopy) has nearly doubled overnight.
>
> My plan is the following:
>
> 1) 15 min prior to the copy time, begin running perfmon on the following
> counters:
> Processor : % Processor Time
> Memory : Pages/sec
> Paging File : % Usage
> Physical Disk : % Disk Time
> Network Interface: Bytes Total/sec
> 2) 15 min past copy time stop running perfmon.
> 3) Import into PAL (Performance Analysis of Logs) for review and to try to
> determine cause/bottleneck of the copy process in order to make a
> recommendation.
>
> I would appreciate any additional suggestions on how I should go about
> this,
> any counters I should add, what I should I be focusing on in my analysis,
> or
> any good artciles/books on the subject etc...
>
> Thanks in advance!
> Keith
>
>