PS Health Monitor

J

JeffG

The other day I obtained the PS Health Monitor for my PS
2002 Server - a great utility I'd recommend for anyone
using PS 2002/3. It's available on MS dowload site.

The problem I have is with the results - specifically the
PDS results. I'm not sure how to interpret the results -
good or bad. Here is the latest:

Last: 4,627 (ms)
Avg: 4,560 (ms)
Max: 13,650 (ms)

I've always stated our PS seems awful slow performance
wise but have never had any proof of this. This numbers
to me seem high? Is this correct? And if so, where
should I be looking to improve performance. The equipment
housing the server is definately server grade.

Any thoughts would be greatly appreciated.

Jeff
 
B

Brian K - Project MVP

JeffG said:
The other day I obtained the PS Health Monitor for my PS
2002 Server - a great utility I'd recommend for anyone
using PS 2002/3. It's available on MS download site.

The problem I have is with the results - specifically the
PDS results. I'm not sure how to interpret the results -
good or bad. Here is the latest:

Last: 4,627 (ms)
Avg: 4,560 (ms)
Max: 13,650 (ms)

I've always stated our PS seems awful slow performance
wise but have never had any proof of this. This numbers
to me seem high? Is this correct? And if so, where
should I be looking to improve performance. The equipment
housing the server is definately server grade.

Any thoughts would be greatly appreciated.

Jeff

Doesn't this say that the average time is 4 seconds and the max was 13
seconds? That does not seem very slow to me.
 
G

Guest

Doesn't this say that the average time is 4 seconds and the max was 13
seconds? That does not seem very slow to me.

--
___
Brian K
Project MVP
www.quantumpm.com
.
That's what you would think...and conceptually that would
be great timing...but when I take out my watch, make a few
updates to a project file and publish the changes it can
take anywhere from 45 seconds to a minute and a half to
save and publish the results. The same goes for opening a
project file. The performance is ridiculous!

I understand MS has a hotfix for this...I'm in the process
of obtaining it and will see if it really makes a
difference or not.

Jeff
 
B

Brian K - Project MVP

That's what you would think...and conceptually that would
be great timing...but when I take out my watch, make a few
updates to a project file and publish the changes it can
take anywhere from 45 seconds to a minute and a half to
save and publish the results. The same goes for opening a
project file. The performance is ridiculous!

I understand MS has a hotfix for this...I'm in the process
of obtaining it and will see if it really makes a
difference or not.

Jeff

Well now that is different information. That is information about how
long it takes to publish the project and is likely based on different
things then how long it takes the pds to process a request. The speed
with which the pds processes things will not tell the whole story so
you cannot draw direct correlations between that and how fast a project
saves/publishes or opens.
 
G

Guest

Well now that is different information. That is
information about how
long it takes to publish the project and is likely based on different
things then how long it takes the pds to process a request. The speed
with which the pds processes things will not tell the whole story so
you cannot draw direct correlations between that and how fast a project
saves/publishes or opens.

--
___
Brian K
Project MVP
www.quantumpm.com
.

ok...so I guess I'm missing the whole point of the PDS
response rate in the Health Monitor. What - real -
purpose does it serve me? If it goes up or down what does
that tell me? Why would I care that the PDS process is 4
seconds but it still takes me a minute and half to open my
project file? What does correlate with the PDS process
time? Again getting back to the value and purpose of this
information. I'm missing it.

Thanks, Jeff
 
B

Brian K - Project MVP

ok...so I guess I'm missing the whole point of the PDS
response rate in the Health Monitor. What - real -
purpose does it serve me? If it goes up or down what does
that tell me? Why would I care that the PDS process is 4
seconds but it still takes me a minute and half to open my
project file? What does correlate with the PDS process
time? Again getting back to the value and purpose of this
information. I'm missing it.

Thanks, Jeff

I would read it that the problem is NOT the project server, server
components themselves that is the issue but rather something like the
SQL server, network bandwidth, network latency, etc.

If the ViewDrop stats were VERY high but the PDS was low then you could
draw the conclusion that the PDS was processing them pretty fast but
maybe there was a big line up of jobs in the viewdrop that was causing
the delay you were seeing in the UI. So each job took at average of 4
seconds but if there were 30 of them then that means 120 seconds. If
yours was the last one then there is your two minutes.

Or it could be that our problem is the VERY large database issue for
which there is a hotfix. :)
 
G

Guest

I would read it that the problem is NOT the project server, server
components themselves that is the issue but rather something like the
SQL server, network bandwidth, network latency, etc.

If the ViewDrop stats were VERY high but the PDS was low then you could
draw the conclusion that the PDS was processing them pretty fast but
maybe there was a big line up of jobs in the viewdrop that was causing
the delay you were seeing in the UI. So each job took at average of 4
seconds but if there were 30 of them then that means 120 seconds. If
yours was the last one then there is your two minutes.

Or it could be that our problem is the VERY large database issue for
which there is a hotfix. :)

--
___
Brian K
Project MVP
www.quantumpm.com
.

I would agree on the latter:
database issue for
which there is a hotfix. :)

The Network issues have been researched and ruled out. As
far as usage - we've done tests where there is only 1 user
publishing a 10 task project and it takes over a minute,
so we know it is not volume. (only 1 file in ViewDrop)

I'm eager to put this hotfix in place and see the
results. Have you heard from people who have implemented
the fix. Has it been successful? I know MS has not done
regression testing on it...and coming from a software
company myself - that is not always a good thing. The
notion of fixing 1 thing to break 10 other things.

But for increased performance I'm willing to accept the
risk...I just hope it is worth it! We will be making the
full backup prior to applying the hotfix.
 
B

Brian K - Project MVP

I would agree on the latter:

database issue for
which there is a hotfix. :)

The Network issues have been researched and ruled out. As
far as usage - we've done tests where there is only 1 user
publishing a 10 task project and it takes over a minute,
so we know it is not volume. (only 1 file in ViewDrop)

I'm eager to put this hotfix in place and see the
results. Have you heard from people who have implemented
the fix. Has it been successful? I know MS has not done
regression testing on it...and coming from a software
company myself - that is not always a good thing. The
notion of fixing 1 thing to break 10 other things.

But for increased performance I'm willing to accept the
risk...I just hope it is worth it! We will be making the
full backup prior to applying the hotfix.

If the network and usage stuff is ruled out then the laser is moving
toward the other thing. :)

Is your database over a gig in size? I know that is one of the big
criteria for the fix I am thinking of.

It is pretty new so I have not talked to anyone that has installed it.

It should not take long to get since you should just call MS tech
support and they will give it to you if they determine that the issues
you are facing are the same ones that the fix was meant to fix.
 
Top