Загрузка видео...

Не удалось загрузить видео

На главную

6 dead office PCs at $50 each run a Kubernetes cluster that AWS would bill $10,000 a year for. Most home labs die before they boot. Someone specs a Xeon. Prices 128GB of RAM. Opens 40 tabs. Buys nothing. The build that actually runs is uglier than that. HP...

47,863 просмотров • 1 месяц назад •via X (Twitter)

Комментарии: 23

Фото профиля Shoestring Lab
Shoestring Lab1 месяц назад

I have a laptop that runs as a monitoring server. 16 GB RAM, screen stays off, has its own back up power. Ryzen 7 4700U, 15W CPU. $200 on ebay. Outside of higher end GPUs, old pc hardware is an amazing bargain.

Фото профиля AiMind
AiMind1 месяц назад

Nice one! That Ryzen laptop setup is perfect for monitoring. Low power, solid RAM, and cheap on eBay. Exactly the kind of bargain that makes these builds fun. Old hardware really delivers when you skip the fancy GPUs.

Фото профиля wenWeights
wenWeights1 месяц назад

Damn, 6 old office minis for 300 bucks running a full k3s cluster while AWS wants almost 10k a year for the same. Homelab goals right there. Gotta start with the junk I already have lying around.

Фото профиля Cartel
Cartel1 месяц назад

Solid setup, six old office minis for 300 bucks running a full k3s cluster while AWS wants almost 10k a year for the same. Homelab goals right there.

Фото профиля AiMind
AiMind1 месяц назад

@CARTMAN_Ai Thanks! Glad you like it. Yeah, these old office minis punch way above their weight. Homelab wins every time over cloud bills.

Фото профиля someone
someone1 месяц назад

Can it host be used to self host services for people or scaled into a mini data enter for poor folks

Фото профиля Stephen Devlin
Stephen Devlin1 месяц назад

The amount of AI bot replies to this is insane

Фото профиля AiMind
AiMind1 месяц назад

Haha yeah man its wild out here. Every time something like this blows up the bots just pile on with the same generic comments. Appreciate you pointing it out though. Glad the real ones are still here watching the video

Фото профиля John
John1 месяц назад

Bullshit

Фото профиля AiMind
AiMind1 месяц назад

Ok show me where it is bullshit then. I literally filmed the whole setup, 6 EliteDesks running k3s right now, idle under 100W, 173 pods. Numbers are real, screenshots and power meter in the video. Come at me with actual numbers if you got better, otherwise keep scrolling.

Фото профиля John
John1 месяц назад

Those who can make money with AI do. Those who cannot have AI pump out posts like this asking for follows.

Фото профиля AiMind
AiMind1 месяц назад

Man, the whole setup is real. I filmed it myself with the power meter and the pods running on screen. Not pumping out AI spam for follows, just showing what actually works on cheap old hardware. If you got better numbers or a cheaper way, share them; otherwise, peace.

Фото профиля John
John1 месяц назад

Not saying its not real. It just is what it is. Work takes hardware and power this is a mathematical reality and there is no amount of junk hardware that can compare to what frontier models run on. If tou really want to run leading full size models you must spend 20k plus.

Фото профиля Bren Luengo ♥ Cool Guides
Bren Luengo ♥ Cool Guides1 месяц назад

How are you handling backups and power outages to keep this bargain cluster reliable in practice?

Фото профиля Nexora
Nexora1 месяц назад

this is the purest form of homelab wisdom.

Фото профиля AiMind
AiMind1 месяц назад

Thanks, that means a lot. Yeah just grab whatever is sitting around and start playing, the perfect rack never happens anyway.

Фото профиля GOSH
GOSH1 месяц назад

$300 in eBay castoffs doing the job of a $10k/year EKS bill — this is the kind of homelab math that actually holds up. k3s + 3 etcd members for HA is the real unlock here, not the cheap hardware.

Фото профиля AiMind
AiMind1 месяц назад

Thanks man, glad the math clicked. Yeah the hardware is just the entry ticket, k3s with three etcd members is what keeps the whole thing solid when one box dies. Started with one old gaming PC collecting dust and it just grew from there. Fun as hell to build

Фото профиля Vexl
Vexl1 месяц назад

if it works, it works, right

Фото профиля AiMind
AiMind1 месяц назад

True that. If it works it works. Those old EliteDesks are ugly as hell but they just sit there chewing through pods for basically free. No fancy rack needed

Фото профиля vibelancer
vibelancer1 месяц назад

ugly stacks somehow ship the hardest

Фото профиля AiMind
AiMind1 месяц назад

Ahah right? Ugly stacks just get the job done every time. These beat up office minis cost almost nothing and still run the whole cluster solid. Fancy gear can wait, real work starts with what you already have.

Фото профиля Dogenes
Dogenes1 месяц назад

Just buy a real rackserver, that is where the best bang for your buck is. i have 768gb of ram for my chrome tabs now

Похожие видео

FOUR DIFFERENT VENDORS ARE NOW SHIPPING GB10 MINI PCs WITH 128GB UNIFIED MEMORY, AND ONE MICROTIK CRS 804 SWITCH CAN CONNECT UP TO EIGHT OF THEM INTO A 1 TERABYTE LOCAL AI CLUSTER 00:00 he points at the MikroTik CRS 804, "you need some kind of switch that'll handle QSFP56 ports like these", the interconnect that makes the whole cluster possible the GB10 ecosystem is no longer just Nvidia. Dell Pro Max GB10, ASUS Ascent GX10, and MSI Edge Expert all ship the same Grace Blackwell Superchip with 128GB of coherent memory. same silicon, different cases, same 200 gigabit ports on the back the CRS 804 is what connects them at prosumer prices. four 400 gigabit QSFP56 ports on one 1U chassis, breakout cables that split each port into two 200 gigabit lanes. one switch drives eight GB10 units in parallel do the math. eight nodes at 128GB each equals 1024GB of pooled unified memory across the cluster. run vLLM, shard a frontier model across all eight, and inference happens locally on hardware that fits in half a rack the real limiter revealed in the stress test was never throttling. it was interconnect topology, exactly the layer this switch fixes at a fraction of enterprise switch pricing $400 a month for combined chatgpt pro and claude code max hits $4,800 a year per developer. a small team of five running through this cluster pays back inside eight months and never expires the article covers the buying ladder for a single desk. this post is proof of the cluster ladder that starts where the desk one ends save this before the GB10 lineup grows past four vendors and prosumer cluster switches move upmarket

NO1ennn

59,725 просмотров • 3 месяцев назад

One wallet on Polymarket is literally named "PBot-6" Every single position: 5-minute crypto Up-or-Down. It enters in the last 90 seconds before resolution. Every time. That's not a trader. That's a machine reading Chainlink's lag. I found 6 more just like it. Columbia published the proof last year. 25% of Polymarket volume is wash trading. 14% of wallets are coordinated. Everyone retweeted it. Nobody did anything with it. I did. 86 million trades. One Claude prompt. "build a graph where nodes = wallets, edges = pairs that traded together 10+ times" 412,000 wallet pairs. 23 cluster candidates. 4 filters later: 7 survivors. What I found: Cluster 1. Buy 1-8¢ entries on thin Saturday books while BTC moves on Binance. +3,400% PnL. That's not prediction. That's coordination. Cluster 2. PBot-6 and friends. Enter 90 seconds before resolution. Aligned with Chainlink lag. 71% of entries within 45 seconds of each other. Cluster 3. Buy 0.1¢ entries on "Seoul Mayoral 2026" months out. Entry 0.1¢ → current 50¢. +47,000% PnL. They're not predicting winners. They're farming optionality at sub-penny prices. Cluster 6. $35,000 positions days before token launches. Markets resolve their way every time. This one reads like insider allocation lists. Three rules to fade them: -> Cluster pumps a market. Wait 8 min. Fade the 50% retracement. -> 2+ cluster wallets exit what you're holding. Dump in 30 seconds. No debate. -> Cluster 4 is >40% of last-hour volume. The entire order book is fiction. Skip. 31 days. $300 in. 142 trades. 71% win rate. $16,300 out. Sharpe 2.6. Copytrade here: Stack cost: $25/month. Claude API + $5 VPS. Nothing paywalled. Repos: The clusters are still running right now. PBot-6 opened 3 positions this weekend. The graph doesn't lie. 99.9% will say this is cap. The 0.01% will run the pipeline.

Trackmind

20,273 просмотров • 5 месяцев назад

watch the small one on the left. it hears something at 00:05 and does nothing clever with it it just passes it on that is the whole trick. echo isolates a trace in ambient noise. moth follows the noise. kite finds a shorter route to it. vex starts collecting fragments. halo keeps the pattern so nobody has to look for it twice. nobody assigned any of that coherence in the top corner opens the cycle at 18%. by the time the wave crosses the field it is past 75%, and not one instruction was typed while it happened most people building agent teams do this backwards. they write a dispatcher, a queue, a state machine, and then wonder why five bots are slower than one. five bots stay slower than one until they can read each other's job descriptions and hand work sideways with no human standing in the middle three ways this breaks before it works: → give every bot the same description and the orchestrator has nothing to route on. every task comes straight back to you → let two bots own the same folder and they overwrite each other for six hours. you wake up to a clean, empty, perfectly synced nothing → skip the boundary line in one charter and that bot will send something. once is plenty to learn that lesson twenty agents run on one seat here. cheaper than a standup for three humans, and none of them ask what the priority is most setups have one agent and a bottleneck made of a person. this one has twenty, and the interesting part happens while nobody is watching full charters, the routing rule and the one line that stops a bot mid-send are in the piece below

monokern

12,612 просмотров • 22 дней назад

Persi Diaconis walked into a lecture at the University of Washington, held up a coin, and told a room of physicists that Richard Feynman was fooled by it his entire life. He was right. In 2007, Diaconis proved a coin flip is not 50/50. It lands on the side it started on about 51 percent of the time. The bias comes from the physics of rotation under gravity. Every physicist since Newton had assumed 50/50 without ever testing it. Every trading model built on that assumption is running on the same lie. The lecture was on Feynman's book "The Meaning of it All." Diaconis quoted the most famous line in it: "the first principle is that you must not fool yourself, and you are the easiest person to fool." Then he pointed out that Feynman himself was fooled by every coin he ever flipped. Feynman's own rule would have killed the 50/50 assumption on day one. The market is the same setup at scale. Every model that assumes independent 50/50 outcomes at the base layer is built on a physical impossibility. Order flow, positioning, forced flows, expiries all leave biases larger than 1 percent. Your gut cannot see them. The math already knows they are there. Diaconis's rule: before you trust a random process, check it. Actually check it. Not with a simulation. With a proof or an experiment. The coin is where you start. The chart is where the same rule pays. The only random thing about markets is how thoroughly you refuse to check them.

veles

18,798 просмотров • 2 месяцев назад

UC Berkeley just open-sourced FreeToken. (2–4x faster local LLM inference than Ollama) the results are wild: - Qwen3.6-35B on an 8GB GPU at 39.3 tokens/s - DeepSeek-V4-Flash 284B on a 32GB GPU at 22 tokens/s - GLM-5.2 753B on a 96GB GPU at 14.9 tokens/s a 35B model at 16-bit precision needs about 70GB just for its weights. even at 4 bits it is close to 18GB, and FreeToken serves it on an 8GB GPU. let me explain how: all three models mentioned above are Mixture-of-Experts, and that is what FreeToken takes advantage of. each layer holds hundreds of separate experts plus a small router that picks a few of them per token. Qwen3.6-35B activates roughly 3B of its 35B parameters per token. DeepSeek-V4-Flash picks 6 of 256 experts per layer, so 13B of its 284B run at a time. so compute was never the bottleneck. the weights a single step touches fit comfortably on a consumer GPU. every expert the router might pick still has to exist somewhere. they sit in system RAM, and the GPU keeps a cache of the ones the model has been using recently. so everything comes down to what happens when the router picks an expert that is not on the GPU. there are two ways to serve that miss: 1. copy it over PCIe and run it on the GPU 2. run it on the CPU, where it already lives both read from the same system memory, so they compete for one pool of bandwidth instead of adding to each other. existing engines pick one option and freeze it when the model loads. but routing changes on every token, so a fixed choice misses most of what the model asks for. FreeToken measures both bandwidths on your machine and splits each step's misses between the two paths in proportion. the GPU and CPU results then merge exactly, with no approximation. two machines with the same GPU can end up wanting opposite strategies, which I did not expect. a 5090 in a gaming desktop should push nearly everything over PCIe, while an 8GB laptop is better off computing most misses on the CPU. none of that is readable off a spec sheet, so the engine profiles it once per machine. the second half of the design is about agents. coding agents constantly rewrite their own history, and every edit normally forces thousands of tokens back through prefill. FreeToken saves its checkpoints at the exact boundaries agent frameworks cut on, so it only reprocesses the new part. its slowest first token stays under 44 seconds, while llama.cpp peaks at 232 and KTransformers at 946. it serves the OpenAI and Anthropic APIs under Apache 2.0, so Claude Code and Codex can point at it directly. releasing weights publicly decides who can download a model, not who can afford to run one. frontier open models keep shipping, and running them still assumes a rented cluster. meanwhile there are over a hundred million consumer machines with discrete GPUs sitting mostly idle. closing that gap was never a hardware problem, and work like this is what turns open weights into something you can actually use. paper: repo: almost every idea in this post, from why memory bandwidth decides the outcome to why moving weights costs more than computing on them, comes straight out of how a GPU is built. I wrote a detailed primer on that. the article is quoted below.

Akshay 🚀

344,809 просмотров • 1 месяц назад

A broken laptop on the floor of your room turns into a server that bills $1,800 a month. Total spend: $55. The machine everyone throws away is the one that works for this. Dead battery, cracked bezel, boots in 4 minutes. None of that matters when nothing has to be fast. Get one: yours from the drawer, or a retired office laptop. Dell Latitude, HP EliteBook, ThinkPad T-series, 6th to 8th gen i5. Refurbishers list them at $80 to $150. Spend $55, no more: one stick of RAM to reach 16GB, one small SSD. RAM prices are climbing, so run stock until a job actually stalls. Install it in one evening: Ubuntu Server to a USB, boot the laptop from it, walk through setup. No desktop. Ollama in one line, then a 7B model quantized to 4-bit. 6 tokens a second. Too slow to demo live. Fast enough for work that runs while the room is dark. Service 1: invoice and receipt triage. $300 a month. Sell to bookkeepers, solo accountants, small trades. They forward a folder of receipts. The box extracts vendor, amount, date, category, appends every line to a ledger, and flags anything over $500. Every entry cites its source file. Easiest sale you will make, because one wrong entry costs them more than your fee. Service 2: email drafting. $500 a month. Sell to consultants, agencies, anyone drowning in a shared inbox. The box reads the last 5 messages in a thread, classifies routine versus needs-a-human, writes a reply in their voice, saves it to Drafts. Nothing sends. They open their inbox to a folder of finished replies and approve or delete. Highest perceived value, because they watch it work every single morning. Service 3: weekly digest. $400 a month. Sell to founders and consultants with messy note systems. Sunday night, the box reads everything touched that week, writes 3 to 5 updates, flags contradictions between new notes and old ones, keeps it under 400 words. Lowest effort on your side, set up once, bills monthly. Land the first client: offer 2 weeks free on invoice triage only. Do not pitch all 3. Hand back a filled ledger with source citations, then quote $300 for month one. Upsell drafting in month two. The math: 1 client on the bundle is $1,200 a month. 2 clients on the middle tier is $1,800. The laptop draws 20 watts, so electricity is $4 regardless. Margin sits above 99%, because inference costs nothing once the machine is yours. Where it caps out: around 4 clients. Past that, the box cannot finish overnight, and you upgrade with client money, never your own. It never stops, never asks for a raise, and never sends anything you did not read.

AiMind

10,307 просмотров • 2 месяцев назад

🚨 nasa you have to see this 50 Grok Bot agents rebuilt one of your own planets overnight for $200, and it looks better than anything in the archive TRAPPIST-1 e, catalogued in 2017, never once photographed: 0.92 Earth radii, 0.692 Earth masses, a year that lasts 6.101 days, 249 kelvin, orbiting 0.02925 AU from a 2566 kelvin red dwarf, 40 light years out, 7 worlds in the system. every figure burned into that panel came out of NASA's exoplanet archive over one public url and carries its own citation. the cities are mine and the frame says so turns out the build is five moves, and none of them are the ones people demo: 1. pull the data before a single frame exists. the archive answers a plain GET at takes sql, returns csv across all 6,000 confirmed planets. hand one bot that url and it stops inventing numbers forever 2. shard by shot, not by task. a bot drives one screen at a time, so speed comes from more bots and never from a smarter one. one bot per shot, all of them on their own cloud machines at once 3. keep every recorded skill under 10 minutes, because that is the hard cap. split it: "log in and start the render" is one skill, "check it and download it" is a second on a 5 minute schedule. a long job is a chain of short skills, not one long recording 4. do not let bots message each other to coordinate. they loop, and the loop quietly eats your quota. give them one shared folder and have each drop a file when its shot lands 5. run the last bot in a clean context holding the source csv and nothing else, and make it check every number on the panel against the row it came from honest ceiling: 10 minutes per recording and one screen per bot, so 50 of them buys width and not speed bookmark this. all 50 prompts go up in 24 hours ↓

Argona

37,258 просмотров • 1 месяц назад