Poor performance on Timesheet Updates

G

GAR

On our EPM system MSP 2003 sp2a (1 front end, 1 database, not using
sharepoint, 250 users, 30 pjms) we are experiencing inconsistent
performance on our timesheet update cycles.

We've had cases where it's taken a local project manager 4 hours to
get through (15 projects) with more than 20 resources. However, the
slow performance is not consistent, a typical speed for this would be
15-20 minutes. The network latency between the database and thick
client is low (less than a millisecond). We haven't been able to
isolate the issue, but feel it could be linked to internal network
traffic / environment , low performing client computers and concurrent
updates happening at the same time.

We've been asked to almost double the number of users accessing the
system and are concerned that our current environment will be
adversely affected. Is our concern valid?

We've been thinking of a couple of infrastructure improvements.
Firstly increase the RAM on the Project Server from 2GB to 4GB. The
other is to add an additional front end in a load-balanced
configuration. I don't think either of these improvements will have
much impact on the issue above as the resource heavy functions of open/
close and the timesheet update cycle rely more heavily on Professional
which connects directly to the database. Is my understanding correct?

Any advice on how to further trouble shoot this type of problem? Has
anyone ever encountered or heard of this issue? I've seen a couple
posts that are similar but no definitive answers.

Thanks,
 
G

Gary L. Chefetz [MVP]

Gar:

This is a tough one to troubleshoot in a forum like this. Inasmuch as you
say the performance issue is inconsistent, can you determine if it happens
only on some plans or for some project managers? If the former were true,
then I'd look at the plans themselves for possible corruption or bloat. If
the latter were true, I'd be looking at the user's hardware, usage habits
and their network connectivity.

Beefing up the server environment may help, but you didn't provide enough
specs for anyone to begin to form an opinion. If the two boxes are rather
dinky, then.... Without more information it's impossible to say.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
G

GAR

The specs for the server environment are:
- 1 MSP front end server
2x 2.8GHz Intel Xeon
2GB RAM

- 1 database server (non-dedicated but MSP is the primary db)
4x899Mhz P3
3GB RAM
Although the database box is older it never appears to
be working hard

- 2 separate terminal services machines for external users
1x 2.4GHz
1GB RAM

2x 2.2GHz
2GB RAM
 
G

GAR

Thanks for your suggestions Gary, we're investigating along those
avenues.

Are there specific symptoms for schedules that are corrupt or
experiencing file bloat? In the past if a schedule is giving us
difficulties, duplicate assignments, accumilating actuals incorrectly
-- we'd assume bloat or corruption and re-import the schedule after
saving as an xml. Are there more subtle symptoms or more specific
symptoms?
 

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