Re: [PATCH] badness() dramatically overcounts memory

iller. I need to read/understand the code a bit more. RSS makes more sense to me as well. To me, it makes no sense to count shared memory, because killing a process doesn't free the shared memory. Regards, Jeff Davis -- To unsubscribe from this list: send the line "unsubscribe

shared memory is over-counted N times when calculating badness()

mount of shared memory, so it's unlikely that process is runaway due to shared memory consumption, and shouldn't add to a process's badness() score. Shouldn't it just use (total_vm - shared_vm) instead, and never even count shared memory? Regards, Jeff Davis - To u

oom_kill.c badness() correction for shared memory

If the OOM killer is invoked, it's almost guaranteed to kill the PostgreSQL parent process first, even if the PostgreSQL processes all combined use much less memory than the "real" bad process (because the same shared memory is counted many times). Regards, Jeff Davis - To u