Windows Server 2012’s redesigned Task Manager, 64 processors in view only - Init

<body> <h1>Windows Server 2012’s redesigned Task Manager, 64 processors in view only</h1> <p>Today, <a href="http://www.twitter.com/dansaap">Daniel van Soest</a> and <a href="http://www.twitter.com/rikvanb">Rik van Berendonk</a> visited <a href="http://www.rug.nl">the University of Groningen</a> to play with Windows Server 2012 on some serious systems.</p> <h2>Serious systems </h2> <p><img style="background-image:none;border-bottom:0px;border-left:0px;padding-left:0px;padding-right:0px;display:inline;float:right;border-top:0px;border-right:0px;padding-top:0px;" title="ProLiant980" border="0" alt="ProLiant980" align="right" src="http://blogs.dirteam.com/blogs/sanderberkouwer/ProLiant980_0D5C4555.jpg" width="160" height="120" />When I talk ‘serious systems’ I’m talking about a fully-fledged HP ProLiant DL980G7 and a Dell PowerEdge R910. The first system was equipped with 8 10-core processors (160 logical processors), 1TB RAM, a couple of disks and a total of 8 power supplies. The Dell system was equipped with a lot less logical processors (only 80) and the same amount of RAM, but in a redundant setup, totaling a mere 512GB.</p> <p>Both systems were connected with 10Gb/s iSCSI to a Storage Area Network (SAN) containing SSDs, where we could play with two 800GB storage pools. This OCZ R4 Z-Drive RM88 was filled with a total of 1.6TB on MLC Nand flash PCI Express cards. </p> <p>Serious systems, right?</p> <p>On both servers we tested new Windows Server 2012 functionality, like Concurrent Live Migrations, NIC teaming, Dynamic Memory, Domain Controller Cloning and a lot of other functionality available through System Center 2012.</p> <h2>Task Manager</h2> <p>During our Dynamic Memory tests (not a new feature for Windows Server 2012, since this feature was introduced with Windows Server 2008 R2 Service Pack 1), we noticed something strange in Task Manager:</p> <p><img style="background-image:none;border-bottom:0px;border-left:0px;padding-left:0px;padding-right:0px;display:inline;border-top:0px;border-right:0px;padding-top:0px;" title="TaskMgrNew64Procs" border="0" alt="TaskMgrNew64Procs" src="http://blogs.dirteam.com/blogs/sanderberkouwer/TaskMgrNew64Procs_452E8978.png" width="524" height="476" /></p> <p>As you can clearly see, the Task Manager in Windows Server 2012 only shows 64 logical processors, while in the bottom right, Task Manager clearly shows we’re dealing with 160 logical processors. (coincidentally the maximum amount of logical processors in VMware’s ESX) <a href="http://software.intel.com/en-us/blogs/2009/01/05/what-does-256-cores-look-like/">Screenshots like the one from Intel a while ago</a>, will not be possible with Windows Server 2012, although you might actually have a system with more than 256 processors in the foreseeable future…</p> <p>Although above about the ‘new’ Task Manager, the ‘old’ Task Manager (still available through <strong>taskmgr.exe</strong>) offers the same functionality:</p> <p><img style="background-image:none;border-bottom:0px;border-left:0px;padding-left:0px;padding-right:0px;display:inline;border-top:0px;border-right:0px;padding-top:0px;" title="OldTaskManager64" border="0" alt="OldTaskManager64" src="http://blogs.dirteam.com/blogs/sanderberkouwer/OldTaskManager64_4BE192FB.png" width="524" height="502" /></p> <h2>Concluding</h2> <p>Anyway, the new Task Manager looks WAY better, so I’m sticking with that.</p><img src="http://blogs.dirteam.com/aggbug.aspx?PostID=6098" width="1" height="1" /> </body>