Performance Monitor on a Widows 2003 Server?

Performance Monitor on a Widows 2003 Server?

• James Manning

  I think there are too many unknowns to give you an answer

  for example - What does the software do if it is doing a lot of number crunching 75% of CPU usage might be expected.

  Another example - Is the target hardware suitable for the application maybe you are using a weak platform what other programs run on the server etc.

  Arnon

  
  
  

• Tom0674

  I would agree with Arnon here, you need to put some work into what your targets should be based on the work your application is introducing versus the capacity in that environment. There's some good info online you should read for doing this:

  http://msdn.microsoft.com/library/default.asp url=/library/en-us/dnpag/html/scalenethowto06.asp

  Without this process you're not going to have good enough information to know whether or not your within an acceptable limit.

  
  
  

• Renzska

  Hey All,

  Well you are both correct. I thought after I posted that that depending on hardware specs and software design and implimentations or what the server is going to be doing web server, database server ect. It really is not enough info. I guess I was shooting for a ball park for most servers which again can very. I have been working on developing a test environment. Also I am mid way through my MCSE, MCDBA and MCSD still to be started. Lots of reading lots of test and lots to learn.

  
  
  

• AaronW62630

  Hi There.

  I have discovered what I believe to be a genuine coding bug in Windows Server 2003 Enterprise x64 SP2 with the Performance Monitor - but haven't been able to find any information regarding a fix, and also dont know of any way to submit it.

  I'm testing a new HP DL580 G5 Dual Quad-Core 64 bit server, and have a clean install of the above OS on it, and SQL 2005 (not too relevant) and running some tests for upgrading our billing system to this platform.

  I have noticed in the Performance monitor, the PhysicalDisk : "Avg. Disk Bytes/Write" (and possibly other similar counters) seems to have a Maximum value of 65536 bytes per second (someone used an int in the coding, instead of something larger ). I discovered this when restoring a large (90GB) sql database, the value is flat-lined at this value, and I *KNOW* it is writing data at a higher rate than this.

  I'm restoring a database through a Gb lan connection, and it's pulling the data through the connection (viewable in task manager) and HP Network Manager at around 240Megabits/second.

  If anyone else can confirm this to be a problem, or if it could be a problem with the RAID driver (It's using the embedded HP Smart Array P400 with 512MB cache etc.) I would love to know.

  Equally - if someone knows a fix for it (it's not a show stopper, but would be nice to resolve for monitoring etc)

  Thanks in advance.

  Daniel.

  
  
• Performance Monitor on a Widows 2003 Server?