slow to save enterprise project

[swissman]

We have a project with about 5000 tasks. The time to save the file before we
moved this project to the enterprise server was about 20 seconds. Now that we
moved this project to teh enterpise server, the save takes about 12 minutes.
Also, trying to save the file to the enterprise server via VPN connection is
not working - i.e. the save operation is not completed after an hour and we
have to kill the project session!

I assume there are many calculations with the OLAP cube and resource pool
that happen during such a save operation. I am wondering, you have any
general guidelines or recommendations how to speed up this painful step or
maybe a method to complete the save operation so the user can logout and then
let the server complete the required calculations in the background
(temporarily freezing any new checkout requests until the computations are
completed)?

Thanks

 

[Marc S.]

Mark,

If your users want to access projects from remote you should consider
working with Terminal Server. Instead of having people establishing an ODBC
connection with the Project Server through the VPN tunnel, let them connect
to the Terminal Server. This will be a much better experience
performance-wise.

As far as the OLAP cube is concerned, nothing happens during the saving or
publishing of a project plan.

Now regarding the slow performance saving the project plan within your LAN,
what does your architecture look like?

Let us know...

Marc

 

[Gary L. Chefetz [MVP]]

Mark:

Let's try some project therapy and see if this helps:

http://www.projectserverexperts.com/Shared Documents/BinaryRebuild.htm

Also, let us know what the total duration of the project is and what service
packs you have installed on the server.