hardware hardware

CPU (CPU)

cpu processor hardware cores threads performance
Plain English

The CPU is the processor, the part of the computer that actually runs programs. Every click, calculation, and app is a list of instructions the CPU works through, billions per second. Modern CPUs have several cores, which are like several workers inside one chip, so the computer can do many things at once. More cores help when lots of work happens in parallel; faster cores help when one task needs to finish quickly.

Technical Definition

The Central Processing Unit (CPU) fetches, decodes, and executes machine instructions.

Key specs:

  • Cores: independent execution units. A 6-core CPU can run six instruction streams at the same time.
  • Threads: simultaneous multithreading (Intel Hyper-Threading, AMD SMT) lets one core run two threads by sharing its execution units. Linux shows these as logical CPUs.
  • Clock speed (GHz): cycles per second. Base clock is guaranteed; boost clock is reached when thermals allow.
  • Cache: small, fast memory on the chip. L1 and L2 per core, L3 shared. A cache hit takes a few nanoseconds; a trip to RAM takes around 100.
  • Instruction set architecture: x86-64 (Intel, AMD) or ARM64 (Apple Silicon, Raspberry Pi, AWS Graviton). Software must be built for the right one.
  • TDP: rough heat output in watts, which drives cooling and power needs.

Hybrid designs: many current Intel and ARM chips mix performance cores and efficiency cores. The kernel scheduler decides which tasks go where.

Virtualization: Intel VT-x and AMD-V must be enabled in firmware for hardware-accelerated VMs. A VM’s vCPUs are threads scheduled on host cores.

Reading CPU load: load average counts tasks running or waiting. Sustained load above the logical CPU count means work is queuing.

Source: lscpu(1) Linux manual page

Inspecting the CPU on Linux 

# Model, cores, threads, virtualization support
$ lscpu
Architecture:          x86_64
CPU(s):                8
Model name:            AMD Ryzen 5 5600U with Radeon Graphics
Thread(s) per core:    2
Core(s) per socket:    4
Virtualization:        AMD-V

# Number of logical CPUs
$ nproc
8

# Load averages over 1, 5, 15 minutes
$ uptime
 10:14:02 up 3 days,  load average: 0.42, 0.37, 0.30

# Live per-core usage (q to quit)
$ htop
In the Wild

CPU questions come up in hardware purchases, VM sizing, and slowdowns. For a homelab hypervisor, core count matters more than peak clock, since you split cores across VMs. For a single-threaded app or a game, per-core speed matters more. When a system feels slow, check whether the CPU is actually the bottleneck before blaming it: high load with low CPU usage in top often means processes are waiting on disk, not the processor. Always confirm the architecture before downloading software; an ARM64 Mac or Raspberry Pi will not run an x86-64-only binary.

← Back to Dictionary