Blog - Konrad Kowalski (rootsher)
posts (112)
- Testing Through Layers: From Code to Infrastructure8/9
Performance Tests and Load Tests: Behavior Under Traffic
A performance test measures system behavior over time, a load test checks expected traffic, and a stress test looks for the breaking point.
- CPU in Kubernetes from the kernel up5/12
CPU Contention: when a process wants CPU and does not get it
With no limit at all a process can sit and wait. All it takes is runnable demand exceeding available capacity - and you only see it in latency.
- Kubernetes from the Inside: Cluster Architecture Basics1/7
Kubernetes Cluster Architecture
Before taking Kubernetes apart into processes, a simple map of the whole - the control plane decides and guards the state, the data plane does the work, and in…
- The Layers of HTTP in the Browser: From fetch() to QUIC7/9
HTTP/2: Multiplexing Changed the Frontend Network Model
The same HTTP semantics, a different wire format. Many parallel requests do not mean many sockets, and stream independence ends at TCP.
- series · 7 parts
Kubernetes from the Inside: Cluster Architecture Basics
A series about what actually makes a Kubernetes cluster work - from kube-apiserver and etcd, through kubelet and CNI, to the managed vs self-managed choice and…
- CPU in Kubernetes from the kernel up4/12
CPU Limits and throttling: what a CPU limit really does
A limit does not pin a container to a core. It gives it a CPU-time budget accounted per period, and once that runs out the kernel throttles it.
- CPU in Kubernetes from the kernel up3/12
CPU Requests in Kubernetes: what they really are
A request is a declaration of demand, not a ceiling. It feeds placement in kube-scheduler and CPU weight on the kernel side.
- Part I: From Prompts to Agentic SDLC7/9
Claude beyond the terminal: three paths
The last upgrade in the core series shows three ways to move beyond the local terminal: remote control of a local session, cloud session and a Managed Agent…
- CPU in Kubernetes from the kernel up2/12
cgroups and CPU: how Linux splits the processor between groups of processes
Group scheduling, cpu.weight and hierarchy - how the kernel divides CPU between groups of processes instead of individual tasks.
- The Layers of HTTP in the Browser: From fetch() to QUIC6/9
HTTP/1.1: Where Waterfalls and Bundling Came From
Bundling, sprite sheets and domain sharding were answers to the cost of many requests. Frontend architecture adapted itself to the limits of the protocol.