Receive Side Scaling - determine whether it is being used

-

hi,

there way determine 100% whether windows 2008 r2 using receive side scaling?  not mean looking @ fact turned on (netsh int tcp show global) versed in this.  want confirm being used.

don't want anecdotally (eg, looking @ cpu usage across single cpu vs multiple cpus) - want know if there way technically, "see" receive side scaling in action.

have 2 identical modern servers - 1 rss enabled , 1 disabled.  apart looking @ settings can't confirm sure 1 using rss , other isn't.  i'd achieve.

i'm looking similar "netstat -t" lets view tcp connections being offloaded (which confirms whether tcp offload being actively used or not).  there way "see" rss being used?  perhaps performance counter or similar?

cheers,
david

i worked out way of doing this.  isn't elegant seems work.

actually, exact technique (the developer owns ndis's rss feature) have recommended windows server 2008 r2, if hadn't have figured out first.  :)

note network drivers don't use ndis interrupts, you'll see "0" "interrupts/sec" counter.  can still feel network activity on these nics switching on "received packets/sec" counter.  counter works on nics, regardless of how driver implemented.

note non-rss miniports don't always use cpu 0 (although that's common choice).

windows server 2012 adds powershell cmdlet, get-netadapterrss, shows more configuration , runtime information.  getting gut-feeling of how rss spreading traffic, perfmon still winner.



Windows Server  >  Platform Networking



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more