Template:Cpulist/doc

cpulist is a template for maintaining lists of microprocessors with separate content and markup.

As of 2024, usage of this template is falling out of favour, due to lack of updates and maintenance, and issues like high overhead (resulting in excessive post-expand include size), lack of customisability (e.g. enabling/disabling columns), difficulty of understanding template code, and inefficiency in data presentation (e.g. many cells with same data in them which could be merged to improve readability).

As a simple example,

results in a table like

Making changes to the cpulist template affects all articles using it, see Special:WhatLinksHere/Template:Cpulist for a list.

Here is the list of cpulist sub-templates:

Template arguments
The first argument to the cpulist template, nehalem in the example, defines the layout of the table. Currently, valid arguments here are
 * lake-e For lists of the (Skylake-SP/F/W/X and Kaby Lake-X) generation of processors, including fields for burst frequency
 * skylake For lists of the Skylake, Kabylake, Coffeelake, etc generation of processors, including GPU field
 * silvermont For lists of the latest (Silvermont/Airmont) generation of low-power processors, including fields for sdp and burst frequency
 * haswell: For lists of the latest (Haswell/Broadwell) generation of processors, showing only the fields that are known to date
 * bridge-e: For lists of the previous (Sandy Bridge/Ivy Bridge) generation of processors, showing only the fields that are known to date
 * bridge: For lists of the previous (Sandy Bridge/Ivy Bridge) generation of processors, showing only the fields that are known to date
 * sandybridge: For lists of the previous Sandy Bridge processors, currently same format as bridge
 * nehalem: For lists of Intel's previous (Nehalem/Westmere) generation of processors, including fields for 'Turbo' mode, L3 cache and Memory Controller
 * nehgfx: like nehalem, but for chips with integrated graphics capability
 * atom: For lists of low-end Atom processors, currently same format as core
 * atomx3: For lists of Atom processors
 * atomgfx: For lists of Atom processors with integrated graphics
 * core: For lists of Intel's previous generation of processors
 * p6: For lists of Intel's p6 generation of processors
 * p5: For lists of Intel's p5 generation of processors

The second argument is the type of processor, defining default contents for many fields that are identical throughout a series of processors. This argument is optional, valid arguments are currently:
 * head: A special argument, resulting in a table header
 * tigerlake, willowcove
 * icelake, sunnycove
 * kabylake_x
 * skylake, skylake_e
 * baytrail
 * haswell
 * ivybridge
 * sandybridge
 * sandybridge_e
 * gulftown
 * gulftownup
 * clarkdale
 * arrandale
 * beckton
 * bloomfield
 * gainestown
 * lynnfield
 * clarksfield
 * jasperforest
 * diamondville
 * silverthorne
 * pineview
 * dunnington
 * harpertown
 * yorkfield
 * wolfdale
 * penryn, penrynulv
 * tigerton
 * clovertown
 * kentsfield
 * woodcrest
 * conroe
 * merom
 * sossaman
 * yonah
 * dothan
 * banias
 * tillamook
 * p5

Other arguments are
 * anchor: An arbitrary HTML anchor that can be assigned to an entry
 * model: The name of the processor
 * sspec or sspec1…sspec8: up to 8 Intel sSpec numbers
 * step1…step8: up to 8 stepping names for the above sSpec numbers
 * freq: Core frequency, can often be determined by fsb and mult arguments, in MHz or GHz
 * uncore: Uncore frequency, in MHz or GHz
 * turbo: Turbo frequencies, as increments in clock multiplier
 * burst: Burst frequencies, in GHz
 * igp: Model of integrated graphics processor
 * gfxfreq: clock frequency of the integrated graphics, if applicable
 * cores: number of processor cores
 * threads: number of processor threads
 * l1: size of the Level 1 Cache, in KB
 * l2: size of the Level 2 Cache, in KB or MB
 * l3: size of the Level 3 Cache, in MB
 * iobus: Type and speed of I/O bus interface, may be expressed as one of
 * fsb: performance of Front-side bus in MT/s, if applicable
 * ht: performance of Hypertransport in MT/s, if applicable
 * qpi: performance of Quickpath interface in MT/s, if applicable
 * dmi: set to 1 if Direct media interface is in use
 * mult: clock multiplier of fsb or base frequency
 * mem: memory interface of integrated memory controller, may be expressed as
 * memspeed: data rate of integrated memory controller
 * volt: core voltage range, usually given as
 * vmin: minimum voltage in volts
 * vmax: maximum voltage (optional) in volts
 * tdp or tdp1…tdp8: Thermal design power in watts
 * sdp: Scenario design power in watts
 * sock or sock1…sock8: Socket, one of 1567, 1366, 1156, 775, 771, M, P, 956, 478, 479, 603, 604 or some others
 * date: release date
 * part or part1…part8: part numbers
 * price: price in USD at the time of release

A special argument is
 * links: If set to any string, wikilinks are added to various units in the table row, usually this is used in the first row of a table