Earlier quoted context omitted.
This is why space is the only acceptable thousands/grouping separator (a non-breaking space when possible). Avoids any confusion.
Space is also confusing! Then it looks like two separate numbers. Underscore (_) is already used as a decimal separator in programming languages and Mathematics should just adopt it, IMO.
GPT‑5.3‑Codex‑Spark
361–370 of 415 posts
Re: GPT‑5.3‑Codex‑Spark
#362Wow, I wish we could post pictures to HN. That chip is HUGE!!!! The WSE-3 is the largest AI chip ever built, measuring 46,255 mm² and containing 4 trillion transistors. It delivers 125 petaflops of AI compute through 900,000 AI-optimized cores — 19× more transistors and 28× more compute than the NVIDIA B200. From https://www.cerebras.ai/chip : https://cdn.sanity.io/images/e4qjo92p/production/78c94c67be9... https://cd…
Re: GPT‑5.3‑Codex‑Spark
#3631000 tokens per second. Crazy. I'm wondering what this leads to. Imagine the massive amount of software that's going to get built. It will be like reinventing the wheel in a million ways. There will be thousands of alternative internet ecosystems to choose from and each one of then would offer every software system, platform and application that one could possibly need; fully compatible with data transferrable across…
Re: GPT‑5.3‑Codex‑Spark
#364Wow, I wish we could post pictures to HN. That chip is HUGE!!!! The WSE-3 is the largest AI chip ever built, measuring 46,255 mm² and containing 4 trillion transistors. It delivers 125 petaflops of AI compute through 900,000 AI-optimized cores — 19× more transistors and 28× more compute than the NVIDIA B200. From https://www.cerebras.ai/chip : https://cdn.sanity.io/images/e4qjo92p/production/78c94c67be9... https://cd…
I can imagine how terribly bad their yield must be. One little mistake and the whole "chip" is a goner.
https://www.cerebras.ai/blog/100x-defect-tolerance-how-cereb...
Re: GPT‑5.3‑Codex‑Spark
#365Earlier quoted context omitted.
> 46,255 mm² To be clear: that's the thousandths separator, not the Nordic decimal. It's the size of a cat, not the size of a thumbnail.
*thousands, not thousandths, right? The correct number is fourty six thousand, two hundred and fifty five square mm.
Re: GPT‑5.3‑Codex‑Spark
#366Every release they claim it writes production code but my team still spends hours fixing subtle bugs the model introduces. The demos are cherry picked and the real world failure rate is way higher than anyone admits. Meanwhile we keep feeding them our codebases for free training data.
Re: GPT‑5.3‑Codex‑Spark
#367Earlier quoted context omitted.
I asked because that's the average power consumption of an average household in the US per day. So, if that figure is per hour, that's equivalent to one household worth of power consumption per hour...which is a lot.
Others clarified the kW versus kWh, but to re-visit the comparison to a household: One household uses about 30 kWh per day. 20 kW * 24 = 480 kWh per day for the server. So you're looking at one server (if parent's 20kW number is accurate - I see other sources saying even 25kW) consuming 16 households worth of energy. For comparison, a hair dryer uses around 1.5 kW of energy, which is just below the rating for most US…
Re: GPT‑5.3‑Codex‑Spark
#368Every release they claim it writes production code but my team still spends hours fixing subtle bugs the model introduces. The demos are cherry picked and the real world failure rate is way higher than anyone admits. Meanwhile we keep feeding them our codebases for free training data.
How would that compare to subtle bugs introduced by developers? I have seen a massive amount of bugs during my career, many of those introduced by me.
Re: GPT‑5.3‑Codex‑Spark
#369Earlier quoted context omitted.
> 46,255 mm² To be clear: that's the thousandths separator, not the Nordic decimal. It's the size of a cat, not the size of a thumbnail.
Thanks, I was acutally wondering how would someone even manage to make that big a chip.
Cerebras has other ways of marking the defects so they don't affect things.
Re: GPT‑5.3‑Codex‑Spark
#370Earlier quoted context omitted.
A first-gen Oxide Computer rack puts out max 15 kW of power, and they manage to do that with air cooling. The liquid-cooled AI racks being used today for training and inference workloads almost certainly have far higher power output than that. (Bringing liquid cooling to the racks likely has to be one of the biggest challenges with this whole new HPC/AI datacenter infrastructure, so the fact that an aircooled rack ca…
> Bringing liquid cooling to the racks likely has to be one of the biggest challenges with this whole new HPC/AI Are you sure about that? HPC has had full rack liquid cooling for a long time now. The primary challenge with the current generation is the unusual increase of power density in racks. This necessitates upgrades in capacity, notably getting 10-20 kWh of heat away from few Us is generally though but if done…