Comment 2 for bug 1666683

Changing status to "Confirmed". I don't think there are any relevant logs for this issue. Here's some anecdotal evidence, though:

# dmesg | grep oom-killer
[1389379.248406] apt-mirror invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=0
[1399428.772409] chrome invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=300
[1421778.653435] java invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=0
[1464982.048253] sh invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=0
[1479431.535969] postgres invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=-900
[1508936.131513] mount invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
[1526250.556039] java invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=0

# cat /proc/uptime
1551384.55 11908654.03

So in the ~7 hours since changing these sysctls, the oom-killer hasn't run, whereas it was running regularly before that.