Re: AWE Memory Question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bob Castleman (nomail_at_here)
Date: 12/10/04 

Date: Fri, 10 Dec 2004 16:17:58 -0500

Speaking of page life expectancy, what is a good value for that? On our
servers that jumps around alot.

Thx,

Bob Castleman
SuccessWare Software

"Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message
news:eiBhBFv3EHA.2156@TK2MSFTNGP10.phx.gbl...
> You could safely give SQL another 2 to 3 GB of dedicated memory provided
> you
> are not running a lot of other apps on teh SQL server. Unless you are
> under
> severe memory pressure, this won't help much. The usual advice on memory
> is
> to look at the data cache hit ratio, but I find on large memory systems
> the
> Page Life Expectancy counter tells me a lot more, especially when the
> cache
> hit ration is above 95%.
>
> Check on IO bottlenecks. Current Disk Queue length is a good stress
> indicator, but also look at Bytes/sec (both read and write separately).
>
> Watch CPU % of course.
>
> Those measurements will tell you the basics of where your SQL server is
> consuming resources and what types of expansion might help.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
>
> I support the Professional Association for SQL Server
> www.sqlpass.org
>
> "Stephen Suley" <stephensuley@hotmail.com> wrote in message
> news:223EFEEE-F3BF-44CF-A4CD-0FB856D2CC7F@microsoft.com...
>> I have a memory configuration question;
>>
>> I am currently running SQL Server 2000 EE on a Windows 2003 Server EE.
>> The hardware is a 4way 2Ghz Xeon MP with 24GB RAM...30+ HDD's.
>> The machine is currently configured to use /PAE in the boot.ini and have
> the
>> SQL Server set to use AWE Memory.
>>
>> My current memory configuration is as follows;
>>
>> 18GB of locked pages in memory from the sqL server;
>> 4Gb left for the OS;
>> and 36GB of Virtual memory allocated;
>>
>> All is working fine and the system has been in production under heavy
>> load
>> without any issues. My question is can I make any modifications to get
> more
>> performance out of SQL Server, specifically allocate more pages in memory
> to
>> sql server and take more away from the OS. Maybe there is a formula or
> ratio
>> that someone could tell me about.
>>
>> Thanks for any ideas or help
>> --
>> Stephen Suley
>> Sys admin
>>
>
>

Relevant Pages

  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • RE: Consolidating instances of SQL server
    ... SQL Server is designed to use memory. ... The maximum amount of memory SQL Server can use varies depending on your ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: The DBMS returned an unspecified error.
    ... | We are using Microsoft's JDBC driver for Java database access to SQL ... | Insufficient memory available. ... even though SQL Server 2000 is configured to use up to the ... the problem is most likely in the MemToLeave ...
    (microsoft.public.sqlserver.jdbcdriver)
  • RE: multiple instances of sql - 2 Gb memory limitation?
    ... The 2GB Memory limitation is per instance and the SQL Server can be ... Configure memory for more than 2 GB in SQL Server ... Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter ...
    (microsoft.public.sqlserver.server)