CPU
8 guides tagged “CPU”.
- How Many vCPUs Does My App Actually Need? Size from the process model and measured CPU time. A single-process web app often needs one or two vCPUs; the database needs headroom and fast disk.
- vCPU vs Core: What's the Difference? A core is physical; a vCPU is a scheduling unit the hypervisor exposes, often one hyperthread. The mapping depends on the instance family.
- Hardware for AI Builders: How the Machine Your Code Runs On Actually Works A zero-jargon guide to computer hardware for people who build with AI: what a CPU, RAM, SSD, GPU, and data-centre server actually do, and how to size a machine for your app.
- What Is a vCPU (and Why Isn't It a Real Core)? A vCPU is a slice of a physical core shared with other customers. Learn about oversubscription, steal time, and burstable instances before you size anything.
- ARM vs x86: Why Your Laptop, Your Server, and Your Cloud Disagree Apple Silicon, AWS Graviton, and Ampere made ARM servers real. Learn what changes when your binary no longer matches your host, and when ARM saves money.
- What Is a CPU (and Why More Cores Isn't Always Faster)? A CPU executes instructions one at a time per core. Learn what cores, clock speed, cache, and instruction sets actually do, and why a slower-looking chip often wins.
- Cores vs Threads: What Hyperthreading Actually Buys You A core executes; a thread is a stream of work. SMT lets two streams share one core, which helps some workloads and slows others. Here is what the spec sheet means.
- How a Program Actually Runs: From Your Python to the CPU What happens between pressing enter and the CPU doing work: bytecode, compilers, syscalls, the kernel, and why containers do not change any of it.