Show HN: SadServers – Test your Linux troubleshooting skills

Post by cube00 » Wed, Oct 26, 2022, 9:45 PM UTC

vsareto wrote: post #51

andrewmcwatters wrote: post #30

My only feedback is that this is unrealistic because today developers wouldn’t try to debug something, they’d just destroy the instance, push a commit and hope it fixed something infra related then recreate it. Why would you need to understand how something works? Just use containers. /s

Developers just need to understand everything because we need developers to do everything and meet all deadlines. We wouldn't dare consider a support role that could troubleshoot it because then there would be no point to having developers that can do everything! /s

Post by jen_h » Wed, Oct 26, 2022, 10:27 PM UTC

DeathArrow wrote: post #55

>Practice for your next SRE/DevOps interview. Are SREs and DevOps tasked with administration of operating systems?

Post by icedchai » Wed, Oct 26, 2022, 10:34 PM UTC

sorongopowa wrote: post #79

Volundr wrote: post #69

Earlier quoted context omitted.

I never cease to be amazed at how few people really realize just how little hardware is often required for getting real work done. You'd be surprised just how much that 2GB vm with a couple cores can handle!

I started with a single 1xx MHz core and 16MB of RAM. And I'm sure some with even less, lol. Supporting your point: Hardware is awesome if you use it wisely.

Post by encryptluks2 » Wed, Oct 26, 2022, 11:04 PM UTC

ilyt wrote: post #35

apawloski wrote: post #13

Based on your architecture diagram it looks like you're spinning up an instance per-user? As you're probably finding now, you will hit AWS limits quickly. You might instead want to have a smaller pool of (larger) servers that you run co-resident VMs on with https://firecracker-microvm.github.io/ . That will avoid account limits and also keep your AWS costs more predictable.

That's kinda nice use case for the WASM machine/linux emulators, then you just need to provide image and user can run it in the browser > You might instead want to have a smaller pool of (larger) servers that you run co-resident VMs on with https://firecracker-microvm.github.io/ . That will avoid account limits and also keep your AWS costs more predictable. I'd imagine (still waiting for it to load lmao) most of it c…

Post by jacooper » Wed, Oct 26, 2022, 11:10 PM UTC

georgyo wrote: post #108

cogman10 wrote: post #94

Earlier quoted context omitted.

Probably a better experience for everyone. You just have to distribute the image (rather than running vms) and the user gets instantaneous responses.

If it is hosted on AWS the bandwidth of distributing the images is likely more than the cost of the compute.