leveling took too long (project server 2003)

L

Lizzie Beth

Project Professional 2003 with SP3
Windows Server 2003 with SP3

I have a project that has 1151 tasks in it. The project manager selected to
level approximately 100 tasks in the plan that have not been published to the
resources. When the leveling starts, the windows task manager shows 100%
utilization on the performance tab and winproj.exe at 99 CPU on the processes
tab. It takes 4 minutes and 30 seconds to level the resources for the 100
tasks. I leveled another project with about the same number of tasks in it
and the utlization was at no more than 13% and took about 5 seconds.
I shutdown the PC and restarted it. The results were the same.
I have looked at the msp_projects, msp_tasks, and msp_resources tables and
validated that the task and resource assignments with the database and
project plan agree.
I selected msp_web_projects, msp_web_assignments, and msp_web_resources. It
appears that only those tasks published show in these tables as the tasks
we're leveling are not in these tables. From what I understand on these
tables, the task_ID and task_name reference the msp_tasks table. There
appears to be some data integrity issues because the task_id and task_name in
msp_web_assignments are not the same task_id and task_name in msp_tasks. The
ID's are off by 1 in some of the items. I am going to request that the
project manager republish the assignments so I can validate that theory.
Has anyone had a project plan that took a long time to level resources and
used 100% utilization? Any other ideas on what to look at or how to correct?

Thank You,
Lizzie
 

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