Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


AWE Counters extremely high


AWE Counters extremely high

Author
Message
Megan Kelly
Megan Kelly
SSC Rookie
SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)

Group: General Forum Members
Points: 35 Visits: 77
I have SQL 2K server with 8GB memory and 11 databases (3 of which are over 15GB)...we'll call server A, and a nearly identical server with 4GB memory and 30 databases (most are between 1 and 3GB)...we'll call Server B.

Server A has extremely high AWE lookup maps/sec (Avg 8472), stolen maps/sec (Avg 15947), unmap calls/sec (Avg 14755), unmap pages/sec (Avg 18858)....and write maps/sec on Avg of 1???

Server B has AWE lookup maps/sec (Avg 153), stolen maps/sec (Avg 795), unmap calls/sec (Avg 776), unmap pages/sec (Avg 915)...and write maps/sec of 0.020 on Avg.

One could argue that the customers on Server A utilize our application far more than the customers on Server B....but with so many customers on Server B I find the rate of activity to be near the same.

Could someone point me in the right direction and help me determine why the AWE counters are so high on Server A?
Paul Randal
Paul Randal
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2159 Visits: 1714
Mu guess would be that the workload is a a lot higher on server A, plus you've got much more AWE memory for SQL Server to use - even so, it looks like the workloads are churning the memory somewhat. If two queries from separate customers are using lots of memory for disparate data, I'd expect to see what you're seeing.

Hope this helps

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
free_mascot
free_mascot
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2873 Visits: 2235
Looks like memory leak problem:

refer the sql server and do the AWE settings as per the articles

http://support.microsoft.com/kb/274750

Make sure you are using sql server enterprise edition; else assign sql server to use fixed memory of 2 gb.

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Paul Randal
Paul Randal
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2159 Visits: 1714
Can you explain why it looks like a memory leak? I'm intrigued...

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
free_mascot
free_mascot
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2873 Visits: 2235
Hello Paul,

FYI:

I was using sql server 7.0 standard edition RAM 2.0 GB. Memory setting Dynamic. Now we have upgraded the server to 4.0 GB.

After the memory upgrade the problem starts; server runs for a few days and suddenly went down. After the investigation we found that sql server eats up memory and there will be no memory left for the OS. After that we have fixed the memory settings to use fixed 2.0 GB and problem solved.

Hence I conclude that here one of the culprit COULD be Memory Leak.

Hope this will satisfy you.

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Megan Kelly
Megan Kelly
SSC Rookie
SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)

Group: General Forum Members
Points: 35 Visits: 77
What can I do to determine what queries/procedures are consuming the most memory? Other than physically running each one myself and monitoring the counters in a dev environment.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search