• Hacker News
  • new|
  • comments|
  • show|
  • ask|
  • jobs|
  • alberth 50 minutes

    Actual title: ”Inside Prometheus: Meta’s Journey to a Gigawatt-Scale Supercluster”

  • ma2kx 12 minutes

    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.

  • lmc 11 minutes

    Is this one of the pilot models they claim R&D tax credits for?

    https://news.ycombinator.com/item?id=49921118

  • markhahn 57 minutes

    shell glob rather than RE? what's the world coming to!

    clod_sux_dik 5 minutes

    [dead]

  • sgvwthry 20 minutes

    Posting this two days before earnings seems to indicate that there is going to be some bad capex news.

    zer00eyz 2 minutes

    Ya dont say.

    Negative Free Cash Flow are the words every one on HN needs to learn.

    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.

    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).

    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.

    4x to 10x for ram +8% for financing +30percent AWS margins. Good luck everyone its gonna get rough out there.

  • xeubie 17 minutes

    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.

    figmert 6 minutes

    > incompetent

    I think that's not incompetence, I think that's by design.

    ctoth 7 minutes

    nft add table inet filter

    nft add set inet filter meta_crawl '{ type ipv4_addr; flags interval; }'

    nft add element inet filter meta_crawl '{ 57.141.0.0/24 }'

    nft add chain inet filter input '{ type filter hook input priority 0; }'

    nft add rule inet filter input ip saddr @meta_crawl tcp dport {80,443} reject with tcp reset

    xeubie 1 minutes

    I did finally block them at the firewall level last night. They are constantly trying to connect anyway.