Like a highway brake failure ramp, you have room for handling failures gentler. So services don't just get outright killed. If you monitor your swap usage, any usage of swap gives you early warning that your services require more memory already.
Gives you some time to upgrade, or tune services before it goes ka-boom.
If your memory usage is creeping up, the way you'll find out that you need more memory is by monitoring memory usage via the same mechanisms you'd hypothetically use to monitor your swap usage.
If your memory usage spikes suddenly, a nominal amount of swap isn't stopping anything from getting killed; you're at best buying yourself a few seconds, so unless you spend your time just staring at the server, it'll be dead anyways.
If there isn't a way to get pass more than a few days, regardless of any choices made, the one lesson simulator is giving is "there's no way an autistic developer can last a few days without burning out". Or from a coworker's perspective: "my coworker is struggling, but there's nothing I can do to prevent burn out in my coworker".
Perhaps tune the choices, and the effects to have a net neutral bonus and penalties to have a longer gameplay loop. Having random weights to the actions might work as well.
> I’ll just remind everyone at the start that this is a respectful debate, and DHH and I tried to get on a call but couldn’t because we were both traveling.
> DHH claims to be an expert on open source, but his toxic personality and inability to scale ...
Yep, real respectful.
I don't even understand the point of the post, other than to shit on the other guy. It doesn't advance any debate or raise any questions.
The post as it is now sounds really decent and a step in the right direction. Let's not air all the dirty laundry happening here, it looks like Matt is trying to do the "right" thing here.
Here is the current iteration of that post from Matt:
"I’ve taken this post down. I’ve been attacked so much the past few days; the most vicious, personal, hateful words poisoned my brain, and the original version of this post was mean. I am so sorry. I shouldn’t let this stuff get to me, but it clearly did, and I took it out on DHH, who, while I disagree with him on several points, isn’t the actual villain in this story: it’s WP Engine and Silver Lake."
he can link to his original post and put the clarification alongside if that's the case. i can change my mind if his actions show he's trying to do "right", but that takes time. for me, it's very important to know that he was even capable of writing the original post.
There's also "diskonaut", a TUI which displays the output like the treemap of WinDirStat. Bonus is that the display is incremental and updates as it scans everything, so you don't need to wait for the complete scan to see how everything looks like.
Written in Rust, and it's a `cargo install diskonaut` away if you have the rust toolchain installed.
Whoa, another (ex?) jed user in the wild. I still install it on new servers, and that was how other admins know if I was ever there. Smaller and faster than installing emacs.
Haha! "In the wild" gave me the visual image of me roaming through a foggy mountain forest with my laptop under my arm and sometimes sitting down and programming in jed and you spotting me and hopefully not shooting me.
NNCP (Bellard's prelude to ts_zip, using similar techniques) is not qualified for Hutter Prize, btw, because hardware and speed limitations specified by Hutter Prize.
"Must run in ≲50 hours using a single CPU core and <10GB RAM and <100GB HDD on our test machine."
Which is an Intel Core i7-620M
I guess that's why the .zip format chucks its catalog index at the end of the archive. But it's still unnatural to use in a streaming format like tapes though.
Gives you some time to upgrade, or tune services before it goes ka-boom.