News for hackers. Stuff that matters.
Re:Court denies motion to dismiss DRAM price fixing case by sigmoid10 on Sunday November 15, 2026 @05:12AM (#50505644)
Not even that, I'd rent out compute. Buying a custom rig for local ML training makes zero sense in 2026. With renting you'll be able to train bigger models/datasets faster on much better hardware while paying far less in total. Especially if you're doing project-based work.
Re:Court denies motion to dismiss DRAM price fixing case by b112 on Sunday November 15, 2026 @06:05AM (#50505974)
If you use a custom disk image too, you can have it boot, apply security updates, reboot, then ssh in within minutes.

Work for however long, shut down. I do this with linode and their GPU VMs. If you shutdown nightly and on weekends, the costs drop dramatically on a monthly spend.

I only need it a few hours per day, so very cheap for custom compute.

Re:Court denies motion to dismiss DRAM price fixing case by LoganDark on Sunday November 15, 2026 @06:07AM (#50505993)
Oh interesting, there are providers that offer variable pricing? (Normally this is bad, but if it allows you to avoid peak pricing, it can be good!)
Re:Court denies motion to dismiss DRAM price fixing case by b112 on Sunday November 15, 2026 @06:16AM (#50506038)
If you delete the linode, you pay nothing. Linode bills hourly. At that point the cost is the custom volume you boot from, and that's cheap.

The custom volume keeps your persistent install, configs, work in progress, etc.

You can programmatically kick off a linode, attach the volume, then boot, as well as delete, all via curl or python.

So not variable rates, but no rates when the beast is deleted.

Re:Court denies motion to dismiss DRAM price fixing case by LoganDark on Sunday November 15, 2026 @06:18AM (#50506053)
Oh, you're just talking about deleting it when you're not using it in general, rather than during peak times. Makes sense.
Re:Court denies motion to dismiss DRAM price fixing case by newComputerWhoT on Sunday November 15, 2026 @02:12PM (#50509729)
The usage pattern i've seen on flexible compute is more aligned with 'I need this process to execute, run it when it's cheap' not 'I'm going to kick off this process, stop it if it get's expensive.' for example AWS Spot Instances
Re:Court denies motion to dismiss DRAM price fixing case by LoganDark on Sunday November 15, 2026 @06:06AM (#50505983)
I mean, there are lots of reasons why you'd want something local, but I agree that the cost makes it unreasonable right now.
Re:Court denies motion to dismiss DRAM price fixing case by sigmoid10 on Monday November 16, 2026 @10:30AM (#50518643)
There used to be lots of reasons. But they've all become moot.
Re:Court denies motion to dismiss DRAM price fixing case by probably_wrong on Sunday November 15, 2026 @07:13AM (#50506370)
Friends of mine wanted to buy a GPU server last year for their new project. Management told them no, that there was a deal with cloud providers and that investing the budget in cloud compute was better.

The project ran out of budget roughly three months in. From what I heard, status meetings consist of everyone getting together once a month, asking "have we gotten any more budget yet? no?", and then wait until the project runs out.

Cloud providers need to make a profit too, and they've gotten very good at ensuring that their clients forget this point. The whole advantage of cloud compute is that you don't pay for the time you're not using it, but once you reach a certain point you're the one covering the overhead for everybody else.