LinuxPerformance
bpftrace one-liners that answer real production questions
Eight bpftrace one-liners for who is busy, which open fails, what keeps starting, how big the reads are and where the CPU goes, with their real output.
iowait, CPU throttling, profiles and eBPF: finding where a Linux box spends its time, with sysstat, perf, bcc and bpftrace.
3 postsRSS feed
Eight bpftrace one-liners for who is busy, which open fails, what keeps starting, how big the reads are and where the CPU goes, with their real output.
A CPU limit below the service's peak shows up as tail latency, not as high CPU. Prove it with cpu.max and nr_throttled, then raise or drop the quota.
vmstat says wa 37%. Read iostat -x the right way (await and aqu-sz, not just %util), name the process with pidstat -d, then cap it with io.max.