Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Ram is about 1/2 in use, four CPUs are all but idle. I tried "Microsoft Server Performance Advisor" with no luck. No entries in the Event Log for hardware failures, etc.

And yet I can click on the start menu and wait 15 seconds for any new attempt. Launching software takes 30 seconds to respond.

The server has an 8 drive WD RE 250 gig each Dell Perc 6 Sata raid array with Intel gigabit network cards.

Anyone have any software titles that could analyze what is going wrong with this server?

share|improve this question
1  
Check the disks. I had a workstation problem once where everything would run slow, and it turned out to be a bad SCSI drive in the RAID setup. The drive didn't show any indicators of being bad, but Dell had me download some diagnostic utility that showed it as bad. They sent out a tech who replaced the drive, and no more slow apps. –  Joe Internet Apr 1 '10 at 23:07

2 Answers 2

up vote 2 down vote accepted

RegMon and probably more likely FileMon would be good starting points. I'd also suggest Performance Monitor for getting ongoing information regarding I/O performance, memory stats and CPU usage. I feel obligated to mention Task Monitor as well, but Process Monitor will give you more information than that. Everything I have mentioned is either built into Windows or free SysInternals tools.

What roles does this machine serve, or what is it's general purpose?

share|improve this answer
    
Generally speaking, it's a file server. –  Dr. Zim Apr 1 '10 at 20:50
    
sysinternals.com for most of those tools btw. –  ManiacZX Apr 1 '10 at 22:50
    
It ended up being heavy vm use on the system drive. I moved the swap file to a separate physical drive and it dropped from 4000 swaps per second to around 100. –  Dr. Zim Mar 15 '11 at 2:44

Something random to check is your path environment variable.

I've had on a few machines something similar to what you seem to be describing where launching applications was very slow with no indications of system performance issues and once the application started it ran fine.

The cause was the path variable had a network location in it that was no longer valid and so as windows was checking all the locations in path, when it hit that one it would sit and wait till it timed out.

In a command prompt run "echo %PATH%" and take a look through the paths listed for anything that isn't on a physical drive in the machine.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.