It seems that Meta didn't mention one aspect of their "next-generation" AI training system: their incompetent web crawler hammers websites while completely ignoring robots.txt. Meta's 57.141.0.0/24 made up about 90% of all requests to my server this past week, and it didn't stop after I blocked it. They continue to make a request every 2 seconds despite me responding with a 403 every time. Truly an engineering marvel that Meta has bestowed upon us.<p>edit: I just checked and they are back to hammering my server at 105 requests per minute. These are the Meta-owned ranges I'm blocking now, in case it helps anyone: 57.141.0.0/16, 57.142.0.0/15, 57.144.0.0/14, 57.148.0.0/15
> incompetent<p>I think that's not incompetence, I think that's by design.
I've blocked Meta, OpenAI and Anthropic and yet they seem to find ways to get back in. It's pretty annoying.
nft add table inet filter<p>nft add set inet filter meta_crawl '{ type ipv4_addr; flags interval; }'<p>nft add element inet filter meta_crawl '{ 57.141.0.0/24 }'<p>nft add chain inet filter input '{ type filter hook input priority 0; }'<p>nft add rule inet filter input ip saddr @meta_crawl tcp dport {80,443} reject with tcp reset
I didn't want to have to put everything behind cloudflare, but this sort of nonsense made it the least bad path forward for us.
> The Ariel variant of GB200 NVL72 pairs each NVIDIA Blackwell GPU with an NVIDIA Grace CPU and 2x NVIDIA ConnectX-7 400G NICs at a 1:1 CPU-to-GPU ratio, letting us deploy 800G of I/O per GPU earlier than the rest of the industry<p>If the 1:1 ratio was purely for I/O (big assumption, very likely wrong), I am curious why they did not just go with ConnectX-8? Other hyperscalers have been shipping NVL72 clusters with ConnectX-8 on roughly the same timeline, and it offers the same 800Gb/s of throughput.<p>Managing a custom Ariel variant (which seems to be a Meta-only build) is not insignificant complexity, I wonder if they had another need for that 2x CPU-GPU ratio in their workloads relative to the stock GB200s.<p>EDIT: I looked, the gb200s NVL72s never have shipped with CX-8s, I made this up. This decision could have totally been due to compute availability and timing
Posting this two days before earnings seems to indicate that there is going to be some bad capex news.
Ya dont say.<p>Negative Free Cash Flow are the words every one on HN needs to learn.<p>Every thing before now, you will look back upon as the happy time. When every year storage, ram and compute grew and the prices went down. Your cloud provider made so much money they paid cash for hardware.<p>Now they borrow at 8% and net margins on ram/storage were around $0.10/GB ... today they sit at over a dollar. (SEE micron's s10's if you want to check the math on that).<p>Forget circular financing, its a circular firing squad because your going to have to figure out where the hell your going to run any of your gear.<p>4x to 10x for ram +8% for financing +30percent AWS margins. Good luck everyone its gonna get rough out there.
I am <i>very</i> lucky to have stocked up on RAM before this happened (256G) but I wished I had doubled or quadrupled that, an upgrade simply isn't going to happen now.
Or hyperscalers revenue will continue to disappoint, there is no $60 trillion market for ai and there will be a glut of capacity for years to come!
Actual title: <i>”Inside Prometheus: Meta’s Journey to a Gigawatt-Scale Supercluster”</i>
Is this one of the pilot models they claim R&D tax credits for?<p><a href="https://news.ycombinator.com/item?id=49921118">https://news.ycombinator.com/item?id=49921118</a>
shell glob rather than RE? what's the world coming to!
Imagine your job is just replacing millions of Dollars worth of hardware every day. I mean there must be a reason the hold 8 GPUs per rack spare.
Yes the reason is they're pushing the GPUs hard so that they fail, and having hot spares saves the job until helping hands can go replace the bad component.
Theres a ton of people working at (neo)clouds doing exactly that