Monday, March 12, 2012

Excessive paging after enabling AWE in SQL server - memgraph1.jpg (0/1)

After enabling AWE in SQL I am noticing a good bit more paging than
before. The attached jpg file is a graph of memory usage.
The configuration for this server is:
IBM x360 w/ 4 x 1.6ghz processors, 8GB memory
Storage: C: and D: partitions internal drives
Data stored on SAN volumes: 5 x 683GB volumes
# databases on this server: 162
boot.ini file has the /3GB and /PAE switches
OS sees all 8GB of memory.
SQL Server has AWE enabled with memory settings:
Min: 0 Max: 5500
As soon as I enabled AWE in SQL, I noticed the following:
(see jpg of the memory usage graph)
1. MemPhysUsage jumps up to almost 80%
(this is the 5500 mark) (in green)
2. PageFileUsage starts climbing up over time. (in pink)
There was little or no page file usage prior to enabling AWE.
Any ideas?
Thanks in advance
jtw
--
http://www.UsenetRocket.comHi,
if the server is only a MS SQL 2k Server, change the
Server properties - dynamicly configure SQL Server Memory -
Give the Server the maximum of memory.
J.K
>--Original Message--
>After enabling AWE in SQL I am noticing a good bit more
paging than
>before. The attached jpg file is a graph of memory usage.
>The configuration for this server is:
>IBM x360 w/ 4 x 1.6ghz processors, 8GB memory
>Storage: C: and D: partitions internal drives
>Data stored on SAN volumes: 5 x 683GB volumes
># databases on this server: 162
>boot.ini file has the /3GB and /PAE switches
>OS sees all 8GB of memory.
>SQL Server has AWE enabled with memory settings:
> Min: 0 Max: 5500
>As soon as I enabled AWE in SQL, I noticed the following:
>(see jpg of the memory usage graph)
>1. MemPhysUsage jumps up to almost 80%
> (this is the 5500 mark) (in green)
>2. PageFileUsage starts climbing up over time. (in pink)
>There was little or no page file usage prior to enabling
AWE.
>Any ideas?
>
>Thanks in advance
>jtw
>--
>http://www.UsenetRocket.com
>.
>

No comments:

Post a Comment