Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 85 views

    Performance Counters

    Uploaded by

    rajiv_ndpt8394
    This document provides guidelines for monitoring various SQL Server performance counters to help optimize performance. It recommends that the % Processor Time, Processor Queue Length, Memory- Pages/sec, Memory- Available Bytes, % Disk Time, Avg. Disk Queue Length, and Buffer Cache Hit Ratio counters average below certain thresholds. It also provides guidelines for disk drive placements, individual disk latency requirements, TempDB configuration, enabling lock pages in memory, and antivirus exclusions to help tune SQL Server performance.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd

    Performance Counters

    Uploaded by

    rajiv_ndpt8394
    85 views2 pages
    This document provides guidelines for monitoring various SQL Server performance counters to help optimize performance. It recommends that the % Processor Time, Processor Queue Length, Memory- Pages/sec, Memory- Available Bytes, % Disk Time, Avg. Disk Queue Length, and Buffer Cache Hit Ratio counters average below certain thresholds. It also provides guidelines for disk drive placements, individual disk latency requirements, TempDB configuration, enabling lock pages in memory, and antivirus exclusions to help tune SQL Server performance.

    Original Title

    performance counters.txt

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides guidelines for monitoring various SQL Server performance counters to help optimize performance. It recommends that the % Processor Time, Processor Queue Length, Memory- Pages/sec, Memory- Available Bytes, % Disk Time, Avg. Disk Queue Length, and Buffer Cache Hit Ratio counters average below certain thresholds. It also provides guidelines for disk drive placements, individual disk latency requirements, TempDB configuration, enabling lock pages in memory, and antivirus exclusions to help tune SQL Server performance.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    85 views2 pages

    Performance Counters

    Uploaded by

    rajiv_ndpt8394
    This document provides guidelines for monitoring various SQL Server performance counters to help optimize performance. It recommends that the % Processor Time, Processor Queue Length, Memory- Pages/sec, Memory- Available Bytes, % Disk Time, Avg. Disk Queue Length, and Buffer Cache Hit Ratio counters average below certain thresholds. It also provides guidelines for disk drive placements, individual disk latency requirements, TempDB configuration, enabling lock pages in memory, and antivirus exclusions to help tune SQL Server performance.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    of 2

    SQL Server performance counters �

    https://www.faceofit.com/sql-server-performance-tuning/

    Processor: % Processor Time Should average below 75% (and preferably below 50%).
    System: Processor Queue Length Should average below 2 per processor.
    For example, in a 2-processor machine, it should remain below 4.
    Memory�Pages/sec Should average below 20 (and preferably below 15).
    Memory�Available Bytes Should remain above 50 MB.
    Memory � Free System Page Table Entries
    Memory � Pages Input/Sec
    Physical Disk�% Disk Time Should average below 50%.
    Physical Disk�Avg. Disk Queue Length Should average below 2 per disk. For example,
    for an array of 5 disks, this figure should average below 10.
    Physical Disk�Avg. Disk Reads/sec Used to size the disk and CPU. Should be
    below 85% of the capacity of the drive.
    Physical Disk�Avg. Disk Writes/ sec Used to size the disk and CPU. Should be
    below 85% of the capacity of the drive.
    Network Interface�Bytes Total/sec Used to size the network bandwidth.
    SQL Server: Buffer Manager� Buffer Cache Hit Ratio Should exceed 90% (and
    ideally approach 99%).
    SQL Server: Buffer Manager�Page Life Expectancy Used to size memory. Should
    remain above 300 seconds.
    SQL Server: Buffer Manager Lazy Writes/Sec
    SQL Server: Buffer Manager Checkpoint Pages/Sec
    SQL Server: Buffer Manager Page writes/sec
    SQL Server: General Statistics� User Connections Used to size memory.
    SQLServer:General Statistics � Logins/sec
    SQLServer:General Statistics � Logouts/sec
    SQL Server: Databases� Transactions/sec Used to size disks and CPU.
    SQL Server: Databases�Data File(s) Size KB Used to size the disk subsystem.
    SQL Server: Databases�Percent Log Used to size the disk subsystem.
    SQLServer:SQL Statistics Batch Requests/Sec
    SQL Server:Latches Average Latch Wait Time (ms)
    SQL Server:Locks Number of Deadlocks/sec
    SQL Server:Locks Lock Requests/sec
    SQL Server:Locks Average Wait Time (ms)
    Paging File %Usage

    Disk Drive Placements:


    Use separate drives for different purposes. (Log File, Data Files, Backup�s &
    TempDB)

    Individual disk latency requirements:


    Database >15ms, Logs> 2ms Tempdb> 2ms

    Do not use the default allocation unit when formatting the Disk drives for SQL
    Server Log files & Data files:
    Format drives with 64k Cluster Allocation Unit

    Antivirus programs:
    These programs can create issues with SQL Server functionality, and it is highly
    important to exclude them from their scan scope, by adding them to the exclusions
    list.
    File types to exclude:
    *.mdf, *.ndf, *.ldf, *.bak

    Always Toggle the maximum memory setting on the SQL Server Instance level
    properties. Ensure at least 2GB � 4GB of RAM is available to the OS
    Note: The maximum memory setting is only for the SQL Server buffer pool, and does
    not include memory requirements for other SQL Server functions like replication
    Services, Agent Job Service etc.

    Storage Planning for TempDB:


    Set the recovery model of TempDB to SIMPLE. This model automatically reclaims log
    space to keep space requirements small.
    Do not allow for TempDB files to automatically grow. This reduces the CPU overhead
    of managing a dynamic file growth.
    Have multiple data file for TempDB (Total Number of TempDB Primary Data File =
    Number of Processors available to SQL)
    Each data file should be of equal size.
    Try to keep each data files in separate disk drives for IO Parallelism.
    TempDB Data and Log files should be kept in faster disk drive (Preferably RAID 1 if
    possible)
    Use RAID-10 or SSD Disks.
    Pre-size TempDB files
    25% of largest DB size.
    Set Auto Growth to fixed size < 200 MB
    You should have the same number of data files as the number of CPUs up to a maximum
    of 8.

    Enable the Lock Pages in Memory Option (Windows)


    This Windows policy determines which accounts can use a process to keep data in
    physical memory, preventing the system from paging the data to virtual memory on
    disk.

    You might also like