Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
The problem: a cgroup running two processes with memory.max set to 900 MiB.
-
I recently ran into a problem with cgroup running two processes, with memory.max set to 900 MiB.
-
Note: Most of this post is me having fun with something that doesn’t run in production.
-
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…
-
I was trying to understand why this Nodejs app was consuming 665 MiB of memory.
-
One of the servers was hitting 90% of CPU utilization.
-
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.
-
A kernel mystery I hit today: load average at 12 on a 2 vCPU machine during a production incident.