slow response from server

E

Ed

Can someone give me an idea of how long an "ideal"
project server implementation would behave when
maintaining projects?

We have been getting response times as follows:
- Opening (~30 task plan) ~15-30 seconds
- get resource list (CTRL+T) (~100 resources) ~55-60
seconds
- save a plan (~30 task) ~15 seconds
- publish a plan ~45-60 seconds

I'm running project Pro on my SQL database server which
is on a GB backbone along with my project server.

When I ping my server I get 1ms response time with no
hops (or one depending on how you look at it).

I'm getting hammered by management that the server is too
slow and must be implemented wrong.... I agree the
response times are not very good but I don't see what the
problem could be...

Help!

thanks,

Ed
 
G

Gary L. Chefetz [MVP]

Ed:

Which version are we talking about? If you're running 2002, the upcoming
service pack may help, although the numbers you're giving us aren't all that
bad.
 
E

Ed

Mr. Chefetz!

It's an honor to get a response from you.
Love the book on MSP Server 2002.

We're still on ver 2002.

If service pack will help, I'll get it ASAP.

If upgrading to 2003 would help greatly with speed, I'll
do it but we've built a lot of web reporting off of the
DB and wouldn't want to have to redo a lot of it without
good reason.

Ed
 
K

Kelley Johnston

Upgrading to 2003 will help a lot of things, and yes it is a lot more
scalable, but I'd check a few obvious items in your SQL server first:

o Is your SQL Server sharing with any other memory-hungry apps, such
as Exchange? A lot of processing overhead goes to adjusting the free
page list, so simply "having enough for each" won't do it. Cut it
away from the pack.

o SQL loves memory -- how much do you have in your server? I'd
guess you're running 512MB or less, perhaps? A gig or two of RAM
tends to do wonders for database performance.

o How many apps are sharing that spindle? If you have a single disk
system, you're suffering needlessly. I'd suggest reconfiguring things
with a few more spindles -- RAID 1+0 is best.

I'd suggest you either put your DBA hat on or find one who can tell
you where your database server is underconfigured. I've heard these
problems reported before, but they were complaining about performance
after they hit the 100,000 project mark, million-plus project tasks...

Cheers,

Kelley
 
Top