← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 8
  1. Swapping a Go heap

    The problem: a cgroup running two processes with memory.max set to 900 MiB.

  2. Swap, memory pressure and the Go GC

    I recently ran into a problem with cgroup running two processes, with memory.max set to 900 MiB.

  3. io_uring without readahead

    Note: Most of this post is me having fun with something that doesn’t run in production.

  4. 1193 backends on WALWrite

    Take a look at this wait-event table: wait_event_type | wait_event | coun ----------------+---------------+------- LWLock | WALWrite | 1193 IO | DataFileRead | 194 IO | DataFileWrite | 4 Lock | frozenid | 2 IO | WalSync | 1 1193 backends on WALWrite made…

  5. A Node.js heap mystery

    I was trying to understand why this Nodejs app was consuming 665 MiB of memory.

  6. Investigating 108,725 forks

    One of the servers was hitting 90% of CPU utilization.

  7. Betting a coffee on a socket leak

    I joined this company a while back and during my first week someone called me to take a look at a mysterious service that would start returning 502s a few days after being restarted.

  8. Sigterm a D state process

    A kernel mystery I hit today: load average at 12 on a 2 vCPU machine during a production incident.