Serious Performance Issue on EPM Timesheet implementation

[Konstantinos Christodoulakis]

Dear all,

We are using Project Server 2007 in an organization of 500 users.
300 of them are using Timesheet Module of Project Server 2007 to complete
their actual work.
Planned work and task assignments per user are stored on Project Plans that
are stored on the Server.
Our Project Teams are working in 9 Big Scale Programs with a lot of tasks.
For Timesheet purposes we created 9 Project Plans with only the basic phases
of the projects.
So every Project Plan has almost 12 Task Lines and assignments per line.
Totally Tasks Lines are 9 * 12= 108 lines.
All these tasks have Start Date=01/01/2010 and End Date=31/12/2010.
For each task work from 1 to 30 users.

Timesheet tasks are prepopulated on Timesheet View.

As the preassigned tasks per user are so many, it takes at least 30 seconds
for the initials assignments to appear on the screen of the user.
In Fridays the workload is very heavy and we had a significant problem.

Even after loading the users have a significant problem, as the tasks are so
many and not grouped per Project, so they are scrolling up and down to
identify their task to fill in the actual hour.

QUESTIONS:
1. What is your proposal to increase the performance for this issue?
2. What should we change on configuration or architecture?

P.S.: I tested the loading of the same data on a Project Server 2010 and it
takes only 3 sec for the page to dispplay the tasks. 2007 takes more than 30
seconds, even if is in MOSS Farm Environment.

Best regards,
Konstantinos Christodoulakis
Project Manager

 

[Christophe Fiessinger [MSFT]]

Have you applied the latest Cumulative Update to your farm?
Have you identified the performance bottleneck? (look at performance
counters in particular on the SQL Server box)
See this to help you with the analysis:
http://blogs.technet.com/projectadm...logs-tool-to-perform-a-farm-health-check.aspx
--
Christophe Fiessinger
Microsoft
http://blogs.msdn.com/chrisfie

"Konstantinos Christodoulakis"

 

[Gary L. Chefetz]

Konstantinos:

IME, migrating your system to an x64 architecture is the best thing you can
do to solve this problem, even assuming that you have the latest patches and
you are following best practices to maintain your SQL databases. The impact
on performance is extraordinary, and it gets you ready for an in-place
upgrade to 2010 when you're ready to take that leap. I strongly urge you to
consider this.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

"Konstantinos Christodoulakis"

 

[Konstantinos Christodoulakis]

Hello Gary,

Our MOSS 2007 Farm (in which Project Server 2007 is installed) is in x64
Architecture.
I installed Project Server 2010 (as a new installation) on a single x64
server and the performance is 1000% better on Timesheet Lines loading.

I'll check to install any latest patch or HotFixes.

My question is:
1. What is so different in Project 2010 and it's loading the same data so
faster than Project 2007? Is it the architecture?

2. How can I bypass this problem until upgrading to Project Server 2010 (in
2 months)?

 

[Gary L. Chefetz]

I think that at least some of what you're seeing is underlying performance
gains with SharePoint 2010 as well as fine tuning in Project Server.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

"Konstantinos Christodoulakis"

 

[Vaso Vukovic]

well just reading this makes one move ro 2010 and I'm not even using
timesheets actively in 2007!!

 

[Gary L. Chefetz]

Everyone should rush to implement 2010 as soon as possible. Every once in a
while a software company hits the nail right on the head, and Project Server
2010 is one those amazing releases that makes it a must have.