Re: HELP: SQL 2000 Queries are 3 times Slower on DUAL XEON vs DUAL PIII
From: Michael S. Perry (michaelperry_at_earthlink..net)
Date: 02/29/04
- Previous message: Andrew J. Kelly: "Re: Restore databases into a new installation of SQL Server"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 29 Feb 2004 00:20:07 GMT
I had same problem, install a read/write cache module, improved
performance by 10 times!
Michael Perry
On 23 Jan 2004 15:56:00 -0800, antjudy01@yahoo.com (Ant Judy) wrote:
>2600 Simple Insert Statements run in 7 Seconds on Hardware 1 (see
>hardware 1 config below) running from the SQL Server Query Analyzer.
>The Same Statements run in 21 Seconds on Hardware 2 (see how killer
>hardware 2 is below). This is without the NIC even plugged in, no
>other users, and no application connecting to SQL (except the query
>analyzer), no blocking, etc. I intentionally chose Insert statments so
>someone won't tell me to check my indexes. Also, I can update stats
>and tune indexes till I'm blue in the face, but remember, all that is
>different between the two systems is the motherboard, ram, processors,
>chassis. Same OS, Same DB Server, Same DB Files, Same Hard Disk type,
>all patched up(yes, I'm on sp3a on 2003 is w2k3 is all patched up). So
>If I had a DB Config problem, I would also have a DB Config problem
>both servers, and ALL OTHER THINGS BEING EQUAL, the DUAL PIII should
>be slower.
>
>Here's what I've tried:
>1) Told SQL to use only CPU 0 and limited SQL to use 1 CPU, then 2,
>then 3, then 4 (SQL Sees 4CPU's due to Hyperthreading). No matter How
>Many CPUS, QUERY IS ALWAYS 21 seconds - that seems meessed up. Yes I
>stop and start the service after each config change
>2) Used MAXDOP(1) in my queries
>3) Turned Off Hyperthreaing in the BIOS and repeated steps 1 and 2
>(with hyperthreading off - sql sees 2 processors). Still Always 21
>seconds.
>4) I have a spare Dual XEON machine in case my primary fails. It's not
>quite as hot (2.4GHZ) w 1GB RAM. It also performs much worse than an
>DUAL PIII, but about the same 21 seconds.
>
>The only common denmominator to the problem is XEON.
>
>----Hardware 1--------------
>DUAL PIII 1GHZ INTEL L440GXG Server Board/INTEL SR2100 Chassis with
>Windows Server 2003 Standard and SQL Server 2000 standard.
>There is 2GB of Intel Approved Registered ECC RAM.
>IBM 10K RPM 36GB SCSI 80-pin
>---------------------
>
>---------------Hardware 2------------------
>DUAL XEON 3.2 GHZ Server (1 MB Processor CACHE) with 4GB of RAM (Intel
>Approved DDR266). The system bus is 533MHZ on an SE7501WV2 INTEL
>Board, INTEL SR2300 Chassis. In the dual processor world, this near
>the top of the line DUAL XEON
>IBM 10K RPM 36GB SCSI 80-pin
>--------------------------------------------
>
>Searching at groups.google.com for "slower sql xeon" yields several
>other people in the world that have this problem. Some of them fixed
>their problem by telling SQL to only use 1 processor, but this has not
>helped me.
>
>If you have any ideas or pointers, I sure would appreciate it
- Previous message: Andrew J. Kelly: "Re: Restore databases into a new installation of SQL Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|