Link to home
Start Free TrialLog in
Avatar of i2mc
i2mc

asked on

Performance almost non-existant how to trace bottleneck

I'm confused.

I have a windows 2003 server that runs a range of applications for video transcoding. Performance is today almost non-existant - system idle process eating 85% - 90% of processor power when 3 other applications are crawling along and not running as they should.

system is dual xeon 2.8Ghz

I've restarted the server. No change.

I can't see what the problem is. Network use is running at 0.5% - 1% on a gig-e interface. Free physical ram is 760MB, average cpu load is 10-20% but there are processor hungry applications taking ages to run and not eating cpu cycles that seem to be free.

system calls per second is running at a mean of 13290 per sec, min 7200, max 24000
context switches per second mean 6400

any ideas as to how best to establish where the bottleneck is or what the problem is??

Roger

ASKER CERTIFIED SOLUTION
Avatar of mdiglio
mdiglio
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
one more thing...what type of server is it ?
some, like HP, will have their own utility to change/verify those network settings
Avatar of i2mc
i2mc

ASKER

>So system idle process at 85-90% is a good thing.

Not really - I see your point but the applications are only running at a few % cpu speed rather than the 20% - 60% they should be - video xcoding is cpu intensive to put it mildly.

> If its set to 'auto' change it to 1000 MB full and set the port to the same.

Would love to - but it's a broadcom netXtreme Gigabit ethernet and the only manual settings are 10/100/half/full ... to get 1000MB you seem to have to set Auto.

It's a dell 2650 FWIW

Roger
Avatar of i2mc

ASKER

The issue was that a network attached storage device had dropped from 22MB/s read speed to 1MB/s - no idea why, all diagnostics are good but the system is in a remote datacentre so hard to check absolutely everything. A reboot of that device cured the problem so you were quite correct to imply that network connectivity was the most likely cause.

Cheers
Roger
Glad you got it working!
Thanks for the points