Drgn: How the Linux kernel team at Facebook debugs the kernel at scale

Re:Drgn: How the Linux kernel team at Facebook debugs the ke... by onion2k on Tuesday December 14, 2021 @02:49AM (#29549284)

There's a huge difference between giving engineers 20% time to work on open source code, and choosing to fix a memory leak by debugging the OS rather than using a health monitor to automatically restart an app. For a start, there's no guarantee that the devs will succeed. It might be a huge waste of time. That's a massive risk.

[ Parent | on HN ]

Re:Drgn: How the Linux kernel team at Facebook debugs the ke... by xorcist on Tuesday December 14, 2021 @03:54AM (#29549636)

"Debugging the OS" sounds not just a little bit pretentious. Perhaps call it "troubleshooting" instead, because that's what's being done. That the problem was found in a driver doesn't make it any different from faulty shell script or a faulty hard disk.

[ Parent | on HN ]

Re:Drgn: How the Linux kernel team at Facebook debugs the ke... by ajuc on Tuesday December 14, 2021 @04:33AM (#29549872)

> That's a massive risk.

Leaving a leak in your code base is a risk too. What if it scales with something outside of your control and suddenly you have to restart every 15 seconds?

[ Parent | on HN ]

Re:Drgn: How the Linux kernel team at Facebook debugs the ke... by onion2k on Tuesday December 14, 2021 @05:40AM (#29550254)

Add more pods.

Its literally the answer to every devOps problem.

(This is a joke btw.)

(... or is it?)

[ Parent | on HN ]

Re:Drgn: How the Linux kernel team at Facebook debugs the ke... by 123pie123 on Tuesday December 14, 2021 @09:11AM (#29551633)

for some.. sadly not a joke

[ Parent | on HN ]

Re:Drgn: How the Linux kernel team at Facebook debugs the ke... by herbst on Wednesday December 15, 2021 @06:04AM (#29564317)

Sure there is, however our company and debug culture also did not take restarts as a solution for memory leaks either.

Sometimes quality matters more than money

[ Parent | on HN ]