memory less used

  • hi ....

    dnt no y no memory is less used .... i hav given 10 gb to sqlserver and remaining to OS ..

    Ram --16 gb as the sqlserver is heavily used...

  • IF we see

    Buffer Counts Buffers

    ------------------------------ --------------------

    Committed 312928

    Target 1310720

    committed = 312928 * 8 / 1024 = 2444,75 MB

    target = 1310720 *8/1024 = 10240 MB

    "Committed. The total number of buffers that are committed in Microsoft Windows NT. The Committed value is the current "size" of the buffer pool. This value includes the physical memory that is allocated if AWE is enabled.

    Target. The target committed count, or how big the buffer pool would like to be. If the Target count is greater than the Committed value, the buffer pool is growing. If the Target count is less than the Committed value, the buffer pool is shrinking. The lazywriter process uses this value to determine whether to grow or to shrink the buffer pool."

    Do you see in perfomn Target Server Memory (KB) and Total Server Memory (KB) ?

    Wich your sql server and OS version ?

    let´s see the sp_configure too....

    $hell your Experience !!![/url]

  • target 10485760

    total 1901312

    Locks(_Total)\Lock Requests/sec

    11484.22032

    OS windows x64

    Awe is enabled

  • Well,

    Slava Oks say ..

    "on 64 bit platform, locked pages, awe mechanism, enable better application's scalability and performance both during ramp up time and over long period of time. "

    http://blogs.msdn.com/slavao/archive/2005/04/29/413425.aspx

    And you said set max and min memory (if your sql server ir only apllication in server, leave more memory ...14 GB no SQL and 2 to OS)

    And you said awe enabled and sql server probably is EE version ..i think your sql it´s ok, but it only uses memory when it need. If awe enabled you can try set min memory to 10 GB and see what´s happend in dbcc memorystatus..obviusly if you can test in your environment.

    $hell your Experience !!![/url]

  • I'm afraid I don't understand the question. Are you concerned that your system is not using enough memory or too much?

    One measure that will tell you if memory is a problem is to look at the page life expectancy. If that's consistently below 300 on most systems, then you're swapping out memory way too much.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • samsql

    to start, can you please post the following info

    SQL server version/edition:

    OS version/edition:

    min memory for sql:

    max memory for sql:

    you say the server has 16GB ram is that correct?

    what exactly do you feel is wrong or causing a problem?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • SQL server version/edition:standard

    OS version/edition:windows x64

    min memory for sql:not set

    max memory for sql:10 GB

    what to do if my Page life expectancy > 300

    Buffer Manager\Page life expectancy = 1398

    1413

    1428

    1443

    1458

    1473

    1488

    1503

    1518

    1533

    1548

    1563

    1578

    1593

    1608

    1623

    1638

    1653

    1668

    1683

    1698

    1713

    1728

  • If your page life expectancy is high, there's not to do but sip some coffee and look for other causes of poor performance. A high page life means that the stuff stored in memory is staying there for a long time. That's good. It means that most processes within your system are able to find the procs & data that the process needs within the memory and those processes are not going to disk to gather information.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • presumably you are using sql2005 standard x64?

    you may want to set the min memory to something sensible!

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply