locked
Recomendations Project Server 2010 Performance (maximum number of Tasks per Project.) RRS feed

  • Question

  • Hi,

    We are currently developing a solution based on Project Server 2010 in Windows Server 2008. We had gone through the Performance recommendations from the following site:
    http://technet.microsoft.com/en-gb/library/ff686784.aspx

    However we are looking for recommended numbers on the Maximum number of Tasks per Project, which this document does not give us.

    As per the client's requirements, we are estimating around 16000 to 30000 Task per project. We know that these numbers are really huge, but need your guidance if Microsoft is actually putting a disclaimer or any upper limit anywhere for the number of Tasks Per Project. Also please note that we have minimum of 23 Custom Fields per Task, this adds to our performance problem.

    We also have major challenge in doing Levelling at Project Professional level.

    I know the following question might fit in this forum, however I feel it is related:

    Are there any recommendation of Performance Requirements in terms of Hardware/Software for the Microsoft Project Professional 2010 Client environment?

    We would like to have your opinion on this.

    Please let me know if you need any additional information.

    Thanks!
    NK Srinivasan

    Tuesday, September 21, 2010 8:40 PM

Answers

All replies

  • With projects that size, you'll want to tune your database as much as possible using as many spindles as possible. You should also consider using the 64bit client on Windows 7 64bit with 4 to 8 meg of RAM on your workstations and a gigabit network backbone between the clients and the server. Are you certain that you need 23 custom task fields? Can you do with less? Can you break up the projects into smaller components? If not, focus on database server performance and client performance.
    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG
    Tuesday, September 21, 2010 9:31 PM
  • Hi NK Srinivasn,

    There is no such thing as a magical number for the maximum number of tasks in a project. There are many other factors that have an impact on the performance. Below are the most important onces:

    • Number of tasks in a project
    • Number of assignments in a project
    • Amount of timescaled data in the project
    • Number of baselines saved
    • Number of custom fields with formula's
    • Use of TaskOnChange event

    Of course, other features also have a slight impact on performance, like the number of dependencies, etc.

    From my experience, you can start noticing a performance drop (opening, saving and recalculating the project) between 1000 and 2000 tasks (depending on other factors like number of assignments, baselines, ...), but you can still work with the projects. At 5000+ tasks, the performance drop can be quite big, but might not be a blocking problem. At 10.000+ tasks, performance gets really bad!
    I've seen project plans with 12.000+ tasks that take up 150MB+, so saving, opening and recalculating is terribly slow.

    But once again, these numbers are only based on my experience and can vary a lot depending on the other factors I mentioned. I've seen noticable performance drops for projects with as little as 500 tasks (lots of baselines, formulas, etc.) and I've heard about people using 20.000+ tasks in a project with no problems (small tasks, no dependencies, baselines, etc.).

    Wouldn't it be a possibility to split those files in smaller, manageable blocks (sub-projects, work packages, ...) and use high-level schedules to manage the relationships between the projects. Some well-defined reports can also help splitting projects in smaller chunks.

    I hope this helps,
    Hans


    My EPM blog: Projectopolis
    Tuesday, September 21, 2010 9:38 PM
  • NK,

    check out this web cast.

    http://www.msteched.com/2010/NorthAmerica/OSP303

    The presenters will go through some stats that may be of interest to you
    Hope this helps


    Marc Soester [MVP] http://marcsoester.blogspot.com
    Wednesday, September 22, 2010 11:01 PM
  • Marc,

    The URL you provided has excellent information.

    Before I looked at the proviced PowerPoint presentation, I had not known that limiting the number of fields in views is a capacity recommendation for PS 2010.

    Can you explain why the number of fields in a view would affect performance? Beyond their being more data elements to retrieve, do views require that much more processing effort in PS 2010 to display (say) 25 fields instead of five? (I'm not quibbling over a few milliseconds of difference.)

    Thanks.

    --John

    Friday, September 24, 2010 2:08 PM
  • Hello NK,

    This article, "Project Server 2007 Performance and Monitoring Best Practices" has exactly what you are looking for.  Open the white paper and seach for "threshholds".

    http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=7d2619c1-7c97-48e3-9e8f-1675fe8c7d55

    You will find the threshold for all sorts of things, like performance goes down when task durations are greater than 2 years, or project has more than 5 resources per task, etc.

    Cheers

    Michael Wharton, MBA, PMP, MCt


    Sincerely, Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA www.WhartonComputer.com
    Monday, September 27, 2010 2:33 PM
  • NK,

    check out this web cast.

    http://www.msteched.com/2010/NorthAmerica/OSP303

    The presenters will go through some stats that may be of interest to you
    Hope this helps


    Marc Soester [MVP] http://marcsoester.blogspot.com
    link is not correct
    Tuesday, November 5, 2013 9:06 PM