Performance between Server and PC

Hi All,
Recently we have an application running for 9 hours+ on an HP DL760 G2 with
8 Processors, 12GB RAM, 4 HDD 15K RPM 142GB running on Raid 1+0. We have
tested with the same database and application on a normal pc which only have
2GB RAM, Pentium Dual Core 930 3GHz, SATA HDD without running RAID, it only
took about 5 hours to complete. Both server and PC is using Windows 2003
Enterprise (32 bit) and SQL 2000 Enterprise (32 bit).
According to the client, their normal operation is working fine. The issue
only happen on that application. But it is weird that the same application
running on normal PC is faster than the server. We just reformat that server,
but the result still took 9hours + to complete.
does anyone know what happen? I have checked all the counter, everything
seem works fine. But I found that the process is pretty fast for 1st 4 hours
then the performance will start degrade.
I also enabled AWE on that server with setting the max memory to 9.6GB RAM
(80% of 12GB). did I leave out something?
I have also tested on HP ML530 G2, Dual Processors and 2GB RAM with RAID 5
(3 HDD 10K RPM). The application still take about 9+ hours to complete.
Any advice is much appreciated. Thanks.
--
Regards,
VenedictVenedict wrote:
> Hi All,
> Recently we have an application running for 9 hours+ on an HP DL760 G2 with
> 8 Processors, 12GB RAM, 4 HDD 15K RPM 142GB running on Raid 1+0. We have
> tested with the same database and application on a normal pc which only have
> 2GB RAM, Pentium Dual Core 930 3GHz, SATA HDD without running RAID, it only
> took about 5 hours to complete. Both server and PC is using Windows 2003
> Enterprise (32 bit) and SQL 2000 Enterprise (32 bit).
> Any advice is much appreciated. Thanks.
When you say "application", what are you referring to? You make
references to the application "completing", which leads me to believe
this is a report or stored procedure.
Have you looked at sysprocesses while this "application" is running? My
hunch is that query parallelism is causing this. If you look at
sysprocesses, you'll likely see several threads with the same spid, some
with a waittype of CXPACKET. You might want to experiment with
different degrees of parallelism.