Konrad Kowalski (rootsher)Principal Platform & Reliability Architect001001111010111011000101111001100001001111011001

Concurrency

posts (4)

  1. CPU in Kubernetes from the kernel up9/12

    NUMA, SMT and cache: when hardware topology starts to matter

    Two workloads can get the same CPU time and do different amounts of work. This is where the CPU abstraction ends and the physics of the machine begins.

  2. 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.

  3. CPU in Kubernetes from the kernel up1/12

    How Linux really gives a process CPU

    A process does not "have CPU". It is ready to run, and the scheduler decides when it actually gets processor time.

  4. Realtime in the Browser: From Polling to WebTransport2/7

    Long Polling: When the Server Delays the Response

    The server does not answer until it has something to send. What appears is a chain of long requests, where the timeout and the cursor are part of the protocol.