Re: AWE Memory Question

• Previous message: Bob Castleman: "Re: AWE Memory Question"
• In reply to: Bob Castleman: "Re: AWE Memory Question"
• Next in thread: Bob Castleman: "Re: AWE Memory Question"
• Reply: Bob Castleman: "Re: AWE Memory Question"
• Messages sorted by: [ date ] [ thread ]

Date: Fri, 10 Dec 2004 16:16:33 -0500

It Depends.

Minimum should be time to populate all of your cache from scratch. Watch
and see what yours is at a low activity time. See how it changes. 10K is a
good high point. Anything that large of bigger can be ignored.

-- 
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Bob Castleman" <nomail@here> wrote in message
news:uZXkvyv3EHA.3504@TK2MSFTNGP12.phx.gbl...
> 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
> >>
> >
> >
>
>

• Previous message: Bob Castleman: "Re: AWE Memory Question"
• In reply to: Bob Castleman: "Re: AWE Memory Question"
• Next in thread: Bob Castleman: "Re: AWE Memory Question"
• Reply: Bob Castleman: "Re: AWE Memory Question"
• Messages sorted by: [ date ] [ thread ]