Post reply

NumaNode Configuration

  • March 21, 2016 at 11:28 am

    #399890

    Hi,

    I have question regarding NumaNode configuration. Last week we made change NumaNode configuration on our SQL Server 2012. before change, 2 NumaNodes were online and 2 NumaNodes were offline. One NumaNode consists 20 CPUs and second NumaNode consists 20 CPUs. and other two were offline.

    As per Microsoft best practice, we made changed to implement all NumaNodes are online and currently all 4 NumaNodes are online and 10 CPUs on each NumaNode.

    after change, when we monitor our Server, we noticed that total wait time increases and processor queue length is also increase from 0 to 3 and sometimes it increases and reaches the value up to 4.

    Please advice...

    Thanks.

  • March 21, 2016 at 3:04 pm

    #1866629

    What's your server power options set to?

    Found this via google pretty quick too:

    Performance Problems with SQL Server 2012 Enterprise Edition Under CAL Licensing

  • March 21, 2016 at 10:00 pm

    #1866657

    Have you manually set the processor affinity or is it set to Automatic ?

    --------------------------------------------------------------------------------------------------
    I am just an another naive wannabe DBA trying to learn SQL Server

  • March 22, 2016 at 8:19 am

    #1866799

    we have power setting set to "high".

  • March 22, 2016 at 8:23 am

    #1866804

    we have unchecked Automatically set processor affinity mask for all processors during change configured 10 CPUs on each server manually.

    And I have also noticed that table lock escalations are decreased. I am not sure is there related to NumaNode configuration?

  • March 22, 2016 at 10:32 am

    #1866861

    Forcing affinity you basically make individual scheduler bound to a particular CPU and the thread on the scheduler will be constrained to run only on that CPU and cannot be moved to run on other CPU.For ex: Scheduler1 is forced to run only on CPU1 ,Scheduler2 only on CPU2 so on and so forth.

    But if you still want to limit the no of CPU's and do not want the scheduler bound to run only a specific CPU you can start SQL Server with TF 8002.

    --------------------------------------------------------------------------------------------------
    I am just an another naive wannabe DBA trying to learn SQL Server

Viewing 6 posts - 1 through 5 (of 5 total)

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