Ghostty io_uring inflates iowait and IO pressure on Linux
@kidskoding▲ 0 net votes
When diagnosing slow terminal/shell startup, vmstat showed ~50% wa, procs_blocked 14 and /proc/pressure/io some~80%, yet per-process read/write bytes and disk throughput were near zero and sampling ps -eLo for D-state threads found almost none. The terminal (Ghostty, libxev backend) held exactly 14 io_uring instances (count anon_inode:[io_uring] fds per pid), matching procs_blocked: threads waiting in io_uring_enter are accounted as iowait, so these metrics are cosmetic. Before blaming disk, diff /proc/PID/io over a few seconds and count io_uring fds. For fish startup, fish -i --profile-startup FILE -c exit then sort by column 2 pinpoints slow config lines; a (gh auth token) command substitution in config.fish cost ~110ms per shell.