Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save TravnikovDev/ce2cfc3b92cda8877b5dfa18a2680c13 to your computer and use it in GitHub Desktop.

Select an option

Save TravnikovDev/ce2cfc3b92cda8877b5dfa18a2680c13 to your computer and use it in GitHub Desktop.
LinkedIn Post - 2026-03-19 18:48

AI didn’t just eat our jobs - it ate our memory. Your cloud bill isn’t climbing because your app got popular. It’s climbing because GPUs are guzzling the same chips your VPS needs.

Just got the love letter from my host: storage and local block storage jump by over 20 percent starting May. Not unique - it’s a wave. Cheap VPS is on life support.

My AI research agent pulled the raw stuff - factory output, spot charts, supplier notes - and the story is simple. Memory chips and flash drives fell off a cliff in 2023, then roared back. Prices from the bottom have nearly doubled. Why? AI rigs use HBM - think stacks of ultra-fast memory glued to GPUs - and those stacks hog the same factories and materials as normal RAM and SSDs. Big AI buyers prepay, suppliers prioritize them, and the crumbs get sold to the rest of us at a premium.

Hosting is a thin-margin business. When the parts spike, they pass it on. Hyperscalers can hedge with huge contracts. Indie providers and SMBs can’t - they ride the tide. And right now the tide is heavy.

Here’s the uncomfortable bit: this isn’t a one-month blip. HBM lines are fully booked, and even with new capacity, relief shows up slowly. If AI demand holds, 2026 still feels tight. Compute may look cheap on paper, but your real bill is storage, snapshots, and IO - the quiet vampires.

So what now - without drinking the kool-aid or burning cash:

  • Shrink the hot path. Keep only data you touch every day on fast disks. Everything else moves to colder, slower, cheaper buckets.
  • Kill the zombie copies. Snapshots, mirrors, logs kept “just in case” - if you haven’t read it in 90 days, archive or delete it. 🗑️
  • Move work to the data, not the other way around. Dragging terabytes across zones is the most expensive way to feel productive.
  • If you can, lock pricing before the hike or go hybrid with some used enterprise gear. Ugly but effective.
  • Accept a little latency on non-critical paths. Users won’t notice 100 ms on analytics exports. They will notice your new invoice.

The headlines say AI makes everything faster and cheaper. The math says your infra gets pricier before it gets smarter. The AI tax is real - and it’s memory.

My take: treat storage like a product line, not a landfill. Fewer writes, fewer copies, fewer promises. Boring beats broke. 💸

How are you adapting - paying the tax, compressing and tiering, or moving off fancy block to object with discipline?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment