Optimum numberof Job Processor Threads

[Raymondd7]

We have a master project with 30 subprojects. I am running into issues during
save wherefiles will hang up in the queue or in some cases Project Pro will
crash and leave files checked out.

Right now we have the maximum number of job processor threads set at the
default 4. Would increasing the number help my situation? Is there a sweet
spot? Is there a downside to increasing the number?

Any help/thoughts would be appreciated.

Thx
R

 

[Ben Howard [MVP]]

Hi Raymond,

Do you get any errors in the queue. There isn't an optimum number, and the
issue could be down to an individual file.

I would try the following.

1. Save each subproject in turn, does ths work successfully?
2. Check the processor load for both the PS and the SQL server, and the I/O
load.

You could try increasing the # of threads, but only if your processor usage
is low. You can use process explorer (ms tool) to see what each thread is up
to...

Regards,

 

[Gary Chefetz]

In addition to Ben's good advice, I'd be curious about the RAM on your
workstation. In my experience, the workstation is the bottleneck. For
arrangements like this you should have a very fast workstation with 2 to 4
gig or RAM.

 

[Ray McCoppin]

I have seen simlar things with master projects. From what I have seen there
is a limit in the 10-15 subprojects in a master project on a 32 bit system.
I think this has something to do with buffers or memory on the client.
Before trying to save you might try to free up as much memory as possible by:
Removing in memory programs (windows messenger)
change your desktop background to solid color
reboot the machine
try to have the least number of calendars as possible in the schedules

The new 2010 64 bit version seems to be able to do this better asumming that
you have more than 4 GB of ram.

Hope this helps