Re: 300MB DB uses 1.4GB RAM!?
- From: "Anthony Thomas" <ALThomas@xxxxxxxxx>
- Date: Sun, 29 Oct 2006 20:51:38 -0600
MEM TO LEAVE is 384 MB by default (-g is 256 MB default). Don't forget
about the other 128 MB set up to manage the possible default 255 worker
threads at 0.5 MB each. This is added to the -g parameter.
DBCC MEMORYSTATUS will tell you how SQL Server memory manager has
partitioned and allocated the BPool.
Anthony Thomas
--
"Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eJxADxc%23GHA.4376@xxxxxxxxxxxxxxxxxxxxxxx
Yeah...but the default mem-to-leave is 256mb, right?to
Data and index pages go into the Buffer pool.
So, if every page was in memory, there's 300mb. Mem-to-leave would have
have been set using -g to 900mb...more
Odd.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Edwin vMierlo" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23%23gm%23gc%23GHA.2340@xxxxxxxxxxxxxxxxxxxxxxx
cache for :
queries / views / stored procedures / tables / indexes ... and a lot
messagewhich SQL holds in memory, when it has the RAM available
"Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23KaCkcc%23GHA.2300@xxxxxxxxxxxxxxxxxxxxxxx
300 MB database, not GB :)
The question is what is using the other 900MB?
My guess (in another thread on a another group - cross posted) is that
mem-to-leave is large and full.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Edwin vMierlo" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
thenews:eq9A3%23Z%23GHA.4980@xxxxxxxxxxxxxxxxxxxxxxx
Unless you need to limit it (if you are running other processes on
tosame
machine), I wouldn't... the more ram SQL takes the better !!
really... you want SQL use all the availabe RAM and cache as much as
possible (in stead of going to disk)
IMHO
"Alex Persky" <alexvi@xxxxxxxxxxxxxx> wrote in message
news:%23V9pJrZ%23GHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
It's going to grab as much as it can and will hardly give it back.number).
Yes, it's excessive. I would recommend set a limit on max amount of
memory
allocation for SQL Server. The default is unlimited (or a very high
SQL Enterprise Management Console and right-click the server and go
courseproperties.
"William Bernat" <nospamplease@xxxxxxxxxx> wrote in message
news:Ol4UcjG%23GHA.3348@xxxxxxxxxxxxxxxxxxxxxxx
SQL Server 2000 running nothing but a 300MB database over the
grabbingof
a
month of continuous use from a single application winds up
1.4GB
jutof
RAM. Is that normal or excessive? (No performance degradation at
all,
a
lot of RAM allocated.)
This is clustered, but the problem has occurred separately on each
node.
Yes, that took over 2 months to test.
-billb
.
- References:
- 300MB DB uses 1.4GB RAM!?
- From: William Bernat
- Re: 300MB DB uses 1.4GB RAM!?
- From: Alex Persky
- Re: 300MB DB uses 1.4GB RAM!?
- From: Edwin vMierlo
- Re: 300MB DB uses 1.4GB RAM!?
- From: Kevin3NF
- Re: 300MB DB uses 1.4GB RAM!?
- From: Edwin vMierlo
- Re: 300MB DB uses 1.4GB RAM!?
- From: Kevin3NF
- 300MB DB uses 1.4GB RAM!?
- Prev by Date: Rebuilding a Failed Cluster Node
- Next by Date: Re: Pros and Cons
- Previous by thread: Re: 300MB DB uses 1.4GB RAM!?
- Next by thread: Re: 300MB DB uses 1.4GB RAM!?
- Index(es):
Relevant Pages
|
Loading