Project Server 2010 performance vs. number of custom fields


It is well known that the amount of custom fields both on task, resource and project level can slow down your Project Server 2010 performance. Microsoft has now made a new article that explains this in more details, which can help you determine whether or not your server farm hardware is apprioriate compared to the number of custom fields that you use. For more info please read below or go this article on Technet: http://technet.microsoft.com/en-us/library/hh297440.aspx

Entity Description/Notes Small Medium Large
1 Projects 100 5000 20000
1 Tasks 17125 856250 3425000
1 Average Tasks Per Project 171.25 171.25 171.25
2 Task Transaction History The number of times status tends to be submitted and approved for any given
task
10 100 1000
1 Assignments 22263 1113125 4500000
1 Average Assignments Per Task 1.3 1.3 1.3
2/3 Approvals Pending Updates Per Manager 50 600 3000
Users 1000 10000 50000
Custom Fields Project (Formula) 3 20 25
Custom Fields Project (Manual) 2 40 50
Custom Fields Task (Formula) Task formula fields tend to take the largest toll on performance because they
need to be computed for each task.
6 12 15
Custom Fields Task (Manual) 4 8 10
Custom Fields Assignment Rolldown 50% 50% 50%
Custom Fields Resource 10 20 25
Custom Fields Look up Table Custom Fields 2 15 100
1 Timesheets (per year) The more you utilize Timesheets the more resource demands that are placed on
the SQL Server
52000 780000 8,320,000
1 Timesheet Lines 5 10 10

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s