Save and Publish Slowdown

C

Carla Evans

In the Save/Publish process, what activities could be degrading the save and
publish performance? Our normal Save and Publish wait times are 4 to 7
seconds per, but occasionally we see 30 to 45 seconds per. We have verified
it's not server, memory or database related. Any ideas?
 
G

Gokul

In the Save/Publish process, what activities could be degrading the save and
publish performance?  Our normal Save and Publish wait times are 4 to 7
seconds per, but occasionally we see 30 to 45 seconds per.  We have verified
it's not server, memory or database related.  Any ideas?

Hi Carla,

There are couple of factors that govern the save/publish.

1. There might be other Project managers publishing their projects,
which can delay your project getting published as it has to go through
queue.
2. Check the Queue status on the PWA and see if anything is blocking
the process or is taking time to finish
3. Sometimes CUBE rebuilding takes time and processes
4. If this happens to the first user of the day, then the server's
initial response and network has to be checked !


If this is a recurring issue, kindly restart the queue/eventing
services and also check for any redundant processes running on the
server.

- Gokul Rajan
Senior EPM PPM Consultant
 
B

Ben Howard

Hi Carla,
The only thing left is network.... Note that the major performance
bottleneck is SQL server I/O. Is something else happening on SQL at the same
time. Also, have you implemented a SQL maintenace plan (re-indexing etc).
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top