Re:Tracking down a memory leak in Ruby's EventMachine
by koenigdavidmj on Friday March 08, 2013 @01:40AM
(#5342319)
That might work for HN, but it doesn't really matter if HN is down for a while. For something like Basecamp (the original 'restart it every few minutes' example, it does not seem nearly as professional.
> We restart HN every 5 or 6 days, or it gets slow (memory leaks). [1]
pg went into more depth about this somewhere, but I don't have the link on hand at the moment. Essentially, the software running it is riddled with memory leaks, but it's more time-efficient to simply reboot it every so often than it is to actually go in and fix it.
[1] https://news.ycombinator.com/item?id=4730251