

CPU definition: A CPU (central processing unit) is the chip that executes the instructions in every program your computer runs. It handles arithmetic, logic, and input/output operations, and every other component in the system routes work through it. People call it the brain of the computer for a reason: without it, nothing else does anything.
A central processing unit is a processor. The two words are used interchangeably in most documentation, and both refer to the same piece of silicon that turns lines of code into electrical operations.
Programs are written as a sequence of instructions. The CPU’s job is to pull those instructions in order, work out what each one is asking for, and carry it out. That loop runs billions of times per second on a modern chip.
Its reach is what makes it central. Storage, memory, network interfaces, and the graphics card all connect back to the processor, and the operating system uses it to schedule and coordinate everything happening on the machine.
| Attribute | Detail |
|---|---|
| Also called | Processor, central processor, microprocessor |
| Primary function | Fetch, decode, and execute program instructions |
| Core components | Arithmetic logic unit, control unit, registers |
| Speed measured in | Gigahertz (GHz), plus instructions per cycle |
| Common form factor | Integrated circuit socketed onto the motherboard |
| Cloud equivalent | vCPU (virtual CPU) allocated to a virtual machine |
The first commercially available microprocessor, the Intel 4004, was released on November 15, 1971. It carried 2,300 transistors and executed roughly 92,000 instructions per second, according to the Smithsonian National Museum of American History. Chips built today carry billions of transistors on a die about the size of a postage stamp. IEEE Spectrum has the full story of how that first chip nearly did not get built.
The processor is one part of a larger system. Our glossary entry on computer hardware covers how the other components fit around it.
Every CPU is built from three functional parts, and a complete CPU definition has to account for all three. They divide the work cleanly between them.
The ALU performs the actual math. Addition, subtraction, comparisons, and logical operations such as AND, OR, and NOT all happen here. When a spreadsheet recalculates a column or a game engine works out where a character should stand, the ALU is doing that work.
The control unit runs the fetch-decode-execute cycle for every instruction. It does not compute anything itself. Instead it directs traffic, telling memory what to hand over and telling the ALU which operation to perform on it.
Registers are tiny, extremely fast storage slots built directly into the processor. They hold the instruction currently being worked on and the memory addresses involved. Three matter most: the program counter (which instruction comes next), the instruction register (the instruction being decoded), and the accumulator (where results land).
Why registers instead of RAM? Speed. Reading from a register takes a fraction of the time it takes to reach random access memory (RAM), so anything the processor needs immediately gets staged there first.
When a program loads into RAM, it sits there as a list of individual instructions. Each instruction has two parts: the operation itself (LOAD, ADD, STORE, JUMP) and the memory address of the data that operation applies to.
The cycle then repeats:
One instruction per cycle sounds slow. A 3 GHz processor runs three billion cycles per second, and modern designs execute several instructions per cycle across multiple pipelines, which is how a chip that only knows how to do simple arithmetic can render video or run a database.
The operating system decides which instructions get to the processor and in what order. Linux and Windows® both use schedulers to divide processor time between competing tasks, and that scheduling is why your music keeps playing while a large file copies in the background.
Three specifications get quoted on every processor spec sheet, and they measure different things.
| Specification | What It Measures | What It Affects |
|---|---|---|
| Clock speed (GHz) | Cycles executed per second | How fast a single task completes |
| Cores | Independent processing units on one chip | How many tasks run truly in parallel |
| Threads | Instruction streams a core can juggle | Efficiency when a core would otherwise idle |
| Cache | Small pool of memory on the chip itself | How often the CPU has to wait on RAM |
A quad-core processor is four processors sharing one package. The operating system can hand each core separate work, so a video export can run on two cores while your browser and email client use the others.
Higher clock speed is not automatically better. A four-core chip at 3.5 GHz will beat an eight-core chip at 2.4 GHz on software that only knows how to use one core, and lose badly on software built for parallel work. Match the chip to what you actually run.
Processor load is also one of the first places to look when a machine feels slow. A pegged CPU produces the same symptoms as a network problem or a memory shortage, which is why rebooting sometimes appears to fix things it has not actually fixed.
Both are processors. They are built for opposite problems.
| CPU | GPU | |
|---|---|---|
| Core count | Typically 4 to 64 | Thousands |
| Core design | Complex, fast, general purpose | Simple, specialized, parallel |
| Best at | Sequential logic, branching decisions, OS tasks | Repeating one operation across huge datasets |
| Typical workload | Operating system, databases, office apps | 3D rendering, video encoding, machine learning |
The CPU is a small team of senior generalists. The GPU is a warehouse of specialists who all do the same task at once. That is why CAD rendering, machine learning training, and video production benefit from GPU acceleration while the operating system itself still depends entirely on the processor. Teams running Revit, AutoCAD, or other design softwareusually need both sized correctly, not one or the other.
The standard CPU definition assumes one physical chip in one machine. Virtualization breaks that assumption. When you run a cloud computer instead of a physical one, you are not assigned a whole chip. You get a vCPU: a virtual CPU, which is a slice of a physical processor’s capacity allocated to your virtual machine by the hypervisor.
One vCPU generally maps to one thread on a physical core. A host server with a 32-core, 64-thread processor can therefore serve a large number of virtual machines, with the hypervisor scheduling access between them. Microsoft®’s Hyper-V® documentation covers the same allocation model in more technical detail.
This matters for two practical reasons.
The first is sizing. Because vCPUs are allocated rather than bought, you can add or remove them as a workload changes, which is not something you can do with a soldered laptop chip. That flexibility is the whole point for seasonal teams and project-based work.
The second is contention. On oversubscribed infrastructure, virtual machines compete for the same physical threads, and performance becomes unpredictable at exactly the wrong moment. Sustained contention also shows up as downtime in the numbers even when the machine is technically running. This is worth asking any provider about directly, and our comparison pages show how we line up against the alternatives. Our cloud desktops allocate resources per virtual machine by workload type rather than per user, and multiple users can share a single desktop where the applications support it.
Where the processing happens also changes what the endpoint needs to be. A thin client with almost no local compute works fine when the CPU doing the work sits in one of our data centers.
Guessing here is expensive in both directions. Under-provision and your team waits on spinning cursors. Over-provision and you pay for capacity that sits idle.
| Workload | Starting Point | Notes |
|---|---|---|
| Browser, email, office documents | 2 vCPU | RAM is usually the constraint before CPU |
| Accounting software, line-of-business apps | 2 to 4 vCPU | Multi-user databases benefit from more cores |
| Development, virtualization, data analysis | 4 to 8 vCPU | Compile and query times scale with cores |
| CAD, 3D rendering, video, machine learning | 8+ vCPU with GPU | The GPU matters more than core count here |
Treat these as starting points, not answers. Check actual utilization after a week of real use, because the gap between what people assume they need and what the monitor shows is often significant.
Hosted applications are the common exception. QuickBooks, Sage, and similar multi-user apps put more load on the processor than their file sizes suggest, particularly during month-end close. Our pricing page breaks down how resources are grouped by workload type, and you can talk to a cloud expert if you want a second opinion on sizing before committing.
A CPU is the processor that fetches, decodes, and executes program instructions. Every other component in a computer depends on it.
What does CPU stand for? CPU stands for central processing unit. It is also called a processor, a central processor, or a microprocessor.
It is the standard analogy and a fair one. The CPU executes instructions and coordinates the other components, though memory, storage, and the GPU all handle work the processor does not.
The arithmetic logic unit (ALU) performs math and logic. The control unit (CU) runs the fetch-decode-execute cycle. The registers hold instructions and memory addresses during processing.
The CPU processes data. RAM holds the data and instructions the CPU is currently working with. Both are required, and neither substitutes for the other.
Not on its own. Clock speed measures cycles per second, but core count, instructions per cycle, cache size, and the software you run all affect real performance.
A vCPU is a virtual CPU: a portion of a physical processor’s capacity assigned to a virtual machine. One vCPU usually corresponds to one thread on a physical core.
Two vCPUs handle browser and office work. Four to eight suit development or data analysis. Graphics-heavy workloads need eight or more plus a dedicated GPU. Our cloud desktop plans are grouped by workload type rather than sold per user.
No. Nothing executes without a processor. Every other component depends on it to schedule and carry out instructions.
Your V2 CloudCare team — real people, on the line.