Project Server slow to save project

B

Brian Tkatch

Project Server 2003 SP2a

One of our Project servers is reportedly slower on a Project save. I'd
like to track this down, but i have no idea what to look for.
(Memory/CPU Usage, Project Resource, DB connectivity). Is there
anything that may help me diagnose this, or some sort of checklist to
go through?

B.
 
B

Ben Howard

Hi Brian, diagonosing this sort of thing is tricky. Its easy to check memory
and CPU utilisation. Saves and publishes for 2003 use the views service
(vwnotify.exe) which is a single threaded application. Check how that is
performing, and check the associated viewdrop folder too for how long the
project is sitting in there. vwnotify could be moved to another processor if
necessary, or indeed to another machine if it's maxing out the existing
server. You can also try the smoketest tool (probably a bit late, this is
good for baselining a system), there is a MOM pack also.

The size of the project and the WAN/LAN latency is also a factor, however,
as you say one of your project servers, it implies you have 2 or more, so I
guess it is a server or project size issue rather than a cable/infrastructure
issue.
 
B

Brian Tkatch

Hi Brian, diagonosing this sort of thing is tricky. Its easy to check memory
and CPU utilisation. Saves and publishes for 2003 use the views service
(vwnotify.exe) which is a single threaded application. Check how that is
performing, and check the associated viewdrop folder too for how long the
project is sitting in there. vwnotify could be moved to another processor if
necessary, or indeed to another machine if it's maxing out the existing
server. You can also try the smoketest tool (probably a bit late, this is
good for baselining a system), there is a MOM pack also.

The size of the project and the WAN/LAN latency is also a factor, however,
as you say one of your project servers, it implies you have 2 or more, so I
guess it is a server or project size issue rather than a cable/infrastructure
issue.
Click to expand...

Thanx.

Currently we have three production server, each for a different area.
One area is mentioning the speed issue. I hope to test out the thiings
that you mentioned.

B.
 
B

Brian Tkatch

Hi Brian, diagonosing this sort of thing is tricky. Its easy to check memory
and CPU utilisation. Saves and publishes for 2003 use the views service
(vwnotify.exe) which is a single threaded application. Check how that is
performing, and check the associated viewdrop folder too for how long the
project is sitting in there. vwnotify could be moved to another processor if
necessary, or indeed to another machine if it's maxing out the existing
server. You can also try the smoketest tool (probably a bit late, this is
good for baselining a system), there is a MOM pack also.

The size of the project and the WAN/LAN latency is also a factor, however,
as you say one of your project servers, it implies you have 2 or more, so I
guess it is a server or project size issue rather than a cable/infrastructure
issue.
Click to expand...

Processor, memory, and network usage during a save is negligable. It
is the save that is slow, not the publish. It goes seven dots in
relatively quickly and then just waits for something for like 10-20
seconds, with the time changing per file.

This is on the same file with roughly the same data, because we
recently (last week) did a restore of the production database into
dev. Both this production and development box are each a single-tier
project server/Database server combo.

Using EditSite to add a new site from the dev box to the prod box is
slow. From prod to dev is fast. So, it seems to be the database part
that is slow.

I'm going to look some more, but i'm not sure what to look for in the
database.

B.
 
B

Brian Tkatch

On Thu, 5 Jul 2007 13:36:01 -0700, Ben Howard
Click to expand...
It goes seven dots in relatively quickly and then just waits for
something for like 10-20 seconds, with the time changing per file.
Click to expand...
Using EditSite to add a new site from the dev box to the prod box is
slow. From prod to dev is fast. So, it seems to be the database part
that is slow.
Click to expand...
<SNIP>

A little more.

I just tested saving a project and looking at the database locks being
held 7 dots in:

There's 5 locks: Type:DB, Mode:S, Status:GRANT, Owner:Sess
The Last TSQLs are:

-MSP_WEB_SP_QRY_GetAllResourceForResId;1
-MSP_WEB_SP_QRY_GetEOrDResourceForResID;1
-IF @@TRANCOUNT > 0 COMMIT TRAN; IF @@TRANCOUNT = 0 SET XACT_ABORT OFF
-MSP_WEB_SP_SEC_CheckSPObjectPermission;1
-sp_execute;1

There's a 2nd set of locks, with the same proc id as
"sp_execute;1"earlier but in a separate object listing:
ProjectServer.dbo.MSP_Attribute_Strings.

For all, the Status is GRANT and the Owner is Xact.

Last TSQL Lock Type Mode Index
sp_execute;1 KEY X I_MSP_ATTRIBUTE_STRINGS
sp_execute;1 KEY X I_MSP_ATTRIBUTE_STRINGS
sp_execute;1 PAG IX I_MSP_ATTRIBUTE_STRINGS
sp_execute;1 TAB IX

These appear on both dev and prod servers. But on Dev it takes a
second or two, whereas prod takes (in the project i was testing)
perhaps 10-20 seconds.

I tested both when noone else was logged on, and no locks were being
help in the ProjectServer database. Because of last weeks
backup\restore, dev and prod currenty have nearly the same data.

I am not sure what else i can check to determine the issue. Would
someone please point me in the right direction? I'd appreciate any
help i could get.

B.
 
Top