February 16, 2010 at 6:45 pm
I'm thinking that it will all boil down to the video card which is likely quite a bit cheaper on the server than on anything else. It takes time to display 900k rows on the screen.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 17, 2010 at 8:16 am
CirquedeSQLeil (2/16/2010)
Here is a reference about disk alignment. SQL server likes the disks aligned and the cluster sizes to be larger than the default settings.
good call on disk alignment.
I notice the maxdop on your server's plan was 1, so 1 thread read all the rows from row 1-n million.
Do you have the plan for your laptop posted or did I miss it?
my gut still says maxdop is the culprit.
Craig Outcalt
February 17, 2010 at 9:23 am
Please find attached the Actual Execution Plan from my home desktop.
Thanks
February 17, 2010 at 9:27 am
Jeff Moden (2/16/2010)
I'm thinking that it will all boil down to the video card which is likely quite a bit cheaper on the server than on anything else. It takes time to display 900k rows on the screen.
It's worth a shot. There could be any number of factors hardware related that could cause this. Low quality ram being another.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 17, 2010 at 9:37 am
for the ziptestserver plan, the QueryPlan DegreeOfParallelism="1", but for the homecexecution plan, it's QueryPlan DegreeOfParallelism="0";
it looks like the rest of the plan is exactly the same though;
Jeff mentioned it might be the video card; if we send the results to file form SSMS, wouldn't that take the display out of the equation?
Lowell
February 17, 2010 at 9:47 am
DegreeOfParallelism="0" means unlimited parallelism (up to number of procs)
I do also note that parallelism = "false" in the xml of both. Not 100% sure if it means what we think.
Try running the same query on both environments with the maxdop query hint.
select * from [dbo].[zip] Option (MAXDOP 1)
If the execution time isn't similar, then I'm totally barking up the wrong tree... no offense to Lowell's Avatar.
:hehe:
Craig Outcalt
February 17, 2010 at 10:47 am
After the MaxDOP suggestion, try barking up Lowell's suggestion to output to file.
Both are good suggestions.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 17, 2010 at 11:07 am
SQLBOT (2/17/2010)
DegreeOfParallelism="0" means unlimited parallelism (up to number of procs)I do also note that parallelism = "false" in the xml of both. Not 100% sure if it means what we think.
Try running the same query on both environments with the maxdop query hint.
select * from [dbo].[zip] Option (MAXDOP 1)
If the execution time isn't similar, then I'm totally barking up the wrong tree... no offense to Lowell's Avatar.
:hehe:
I ran the server query to screen with MAXDOP set to 0, which is the same as the desktop, and the time to run the query was the same as when MAXDOP was set to 1 on the server.
February 17, 2010 at 11:14 am
isuckatsql (2/17/2010)
SQLBOT (2/17/2010)
DegreeOfParallelism="0" means unlimited parallelism (up to number of procs)I do also note that parallelism = "false" in the xml of both. Not 100% sure if it means what we think.
Try running the same query on both environments with the maxdop query hint.
select * from [dbo].[zip] Option (MAXDOP 1)
If the execution time isn't similar, then I'm totally barking up the wrong tree... no offense to Lowell's Avatar.
:hehe:
I ran the server query to screen with MAXDOP set to 0, which is the same as the desktop, and the time to run the query was the same as when MAXDOP was set to 1 on the server.
That raises a few questions.
1. How many procs are allocated to SQL server in the properties?
2. Did you run the query only once, or multiple times?
3. And with the maxdop change did you clear the cache prior to executing the query?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 17, 2010 at 11:31 am
CirquedeSQLeil (2/17/2010)
isuckatsql (2/17/2010)
SQLBOT (2/17/2010)
DegreeOfParallelism="0" means unlimited parallelism (up to number of procs)I do also note that parallelism = "false" in the xml of both. Not 100% sure if it means what we think.
Try running the same query on both environments with the maxdop query hint.
select * from [dbo].[zip] Option (MAXDOP 1)
If the execution time isn't similar, then I'm totally barking up the wrong tree... no offense to Lowell's Avatar.
:hehe:
I ran the server query to screen with MAXDOP set to 0, which is the same as the desktop, and the time to run the query was the same as when MAXDOP was set to 1 on the server.
That raises a few questions.
1. How many procs are allocated to SQL server in the properties? - Eight
2. Did you run the query only once, or multiple times? - Multiple times.
3. And with the maxdop change did you clear the cache prior to executing the query?
I used this query to make the change as the one suggested above did not change the MAXDOP.
How do i clear the cache?
sp_configure 'show advanced options', 1;
GO
RECONFIGURE WITH OVERRIDE;
GO
sp_configure 'max degree of parallelism', 0;
GO
RECONFIGURE WITH OVERRIDE;
GO
February 17, 2010 at 11:38 am
The query provided used a query hint that forces max degree of parallelism for that query only.
Through SSMS, right click the server, select properties from the context menu. Click on Processors on the left of the new window. How many processors show in the screen on the right now?
As for clearing cache:
DBCC FreeProcCache is one method.
Since it appears this is a dev server - you should be ok to perform that command. If it is a prod server, I would be careful about when you run that command since it clears the cache.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 17, 2010 at 12:03 pm
Eight processors
February 17, 2010 at 12:18 pm
isuckatsql (2/17/2010)
Eight processors
Go ahead and try the query with output to file.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 17, 2010 at 12:50 pm
Just couple of stupid questions. I already know the answer but just for the sake of it..
1. Do you see any Wait for resources while running on the server?
2. What is the RAID configuration you are using?
-Roy
February 17, 2010 at 5:53 pm
Server SSMS query to file - 35 seconds
Desktop SSMS query to file - 25 seconds
Viewing 15 posts - 16 through 30 (of 66 total)
You must be logged in to reply to this topic. Login to reply