Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In an era of multi-core, hyperthreaded CPUs, "Processors" is now an ambiguous term. Does the processor refer to a threads (from Hyperthreading), cores, or sockets (physical CPUs).</p> <p>Windows recognises logical processors (LP) as the basic compute platform - giving one LP for each hyperthread within a core, and then multiplied for each core, which is finally multiplied by the number of sockets.</p> <p>The easiest way in Windows to reduce the LP count is to use the /NUMPROC option. In this example itc creates a maximum number of processors of 8.</p> <blockquote> <ol> <li>Backup bcdedit /export c:\Backup\bcd.bak</li> <li>List of current entries bcdedit /v</li> <li>Copy of existing config bcdedit /copy {current} /d "Windows 2008 R2 with NumProc" The current is a "well known" identifier . This also returns the Id that is created. So that can be used directly</li> <li>List of entries bcdedit /v</li> <li>adding parameter to new entry To set maximum number of processors<br> bcdedit /set {new_ID} NUMPROC 8 </li> <li>Changing default entry bcdedit /default {new_ID}</li> </ol> </blockquote> <p>But the danger of this strategy is for example on a 4 core system with HyperThreading enabled then only one processor (socket) is used. Since the first 8 LPs (0..7) will be hyperthreaded cores on the first processor. So you are not really emulating an 8 way system - but a 1 way - 4 core system with HyperThreading enabled.</p> <p>If this doesn't fit your model other options are</p> <ul> <li>Disable HyperThreading in the BIOS - this reduces the LP count per core so helping distribute the load over cores and sockets.</li> <li>Does the System BIOS support reducing the core counter per processor? If so this will help distribute loads over sockets.</li> <li>Building your system within a virtual environment and limiting physical resources from that perspective.</li> </ul> <p>If you are dealing with more than 64 Logical Processors under Windows then that introduces Processor Groups and that add another layer of options.</p>
    singulars
    1. This table or related slice is empty.
    1. POLimiting the number of processors available to Windows Server 2008 R2
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USIan Jespersen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POLimiting the number of processors available to Windows Server 2008 R2
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis helps, thanks. I know that 16 of my 32 LPs are the result of hyperthreading, so I'll have to disable Hyperthreading via BIOS before limiting the number of LPs further through the boot option. That way I'm actually mimicking the number of cores I want rather than simply removing threads.
      singulars
      1. PO
      1. USSean Long
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload