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.
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
show comments
sgvwthry
Posting this two days before earnings seems to indicate that there is going to be some bad capex news.
show comments
islewis
> 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
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.
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.
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
alberth
Actual title: ”Inside Prometheus: Meta’s Journey to a Gigawatt-Scale Supercluster”
lmc
Is this one of the pilot models they claim R&D tax credits for?
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.
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
Posting this two days before earnings seems to indicate that there is going to be some bad capex news.
> 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
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.
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.
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
Actual title: ”Inside Prometheus: Meta’s Journey to a Gigawatt-Scale Supercluster”
Is this one of the pilot models they claim R&D tax credits for?
https://news.ycombinator.com/item?id=49921118
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.