Hacker Dudes// alternate deck. same feed.
FEED ~14/h Δ0 ────:──── LINK ░ SIGNAL
94%
SPOOLED 0/45 CYCLE 61339.947.164.10
Google open-sources TorchTPU, a native PyTorch back end for TPUsgithub.com
379pts/91 comments/6d/─
by ilreb / hn> / « feed
▲▼ Lucasoato16:48 hn>

Are there TPUs outside Google Cloud?

▲▼ sschueller16:55 hn>

Google coral USB and m.2 devices are TPUs.

▲▼ boulos17:07 hn>

Only in marketing name. They're not related otherwise.

▲▼ Archit3ch18:27 hn>

"Have you seen any software run on Coral TPUs?"

"No, but I have seen the house that the project built, and it is terrific." ~ some Google director

─ 2 more ─
▲▼ westurner16:55 hn>

TPU / neural compute accelerator / Math coprocessor;

"OpenTPU: Open-Source Reimplementation of Google Tensor Processing Unit (TPU)" https://news.ycombinator.com/item?id=44111452

From https://news.ycombinator.com/item?id=45848676 :

>How does Cerebras WSE-3 with 44GB of 'L2' on-chip SRAM compare to Google's TPUs, Tesla's TPUs, NorthPole, Groq LPU, Tenstorrent's, and AMD's NPU designs?

There are TPUs made out of silicon carbide with standard fab.

There is in-flight tensor processing with photons, but that's not quite a TPU.

▲▼ hackernudes17:59 hn>

I think the commenter was asking if Google sells TPU chip hardware to use outside of Google's own infrastructure and cloud.

▲▼ boulos17:08 hn>

Yes. Google is famously selling TPUs on prem to big customers (e.g., Anthropic) and Crux AI is now a venture to do just that.

▲▼ goda9017:55 hn>

Maybe just marketing, but they call the NPUs in their Pixel phones "TPUs"

▲▼ fulafel05:37 hn>

TPUs are really matrix processors (they process 2d tensors right?), it's technically fair to call most matrix processors TPUs.

▲▼ npalli16:51 hn>

Interesting, Amazon doing the same for AWS Trainium.

https://github.com/aws-neuron/torch-neuronx

▲▼ AnotherGoodName18:48 hn>

Pytorch conference is happening today for explaining the coincidental timing

▲▼ sroussey18:51 hn>

That explains the 5x speed increases huggingface mentioned for Mac using metal.

─ 1 more ─
▲▼ yipinwong17:07 hn>

Dumb question from non-AI engineer.

Is this somehow Google's answer to today's best DeepSeek open-sourcing inferencing engine?

▲▼ bitpush17:15 hn>

I dont think big companies like Google react to news like that. Very likely this was meant to go out on Tuesday for weeks now. And it just happened to have coincided with another news.

▲▼ Tanjreeve17:20 hn>

They do different things and sit in different parts of the stack (training vs inference). TorchTPU seems more like a play to get more people familiar with Googles TPU chips as they want to sell them to people outside of google.

▲▼ beardedetim18:22 hn>

Yeah I'd assume this is to allow us to train on their TPUs with torch instead of needing to rent a GPU

─ 1 more ─
▲▼ mathisfun12317:47 hn>

lol no this is a replacement for https://github.com/pytorch/xla

▲▼ JacobAsmuth17:58 hn>

Yeah they read the news this morning and whipped up a quick Torch->XLA translation layer and coordinated with four different inference engines (who also all wrote their own blog posts) and shoved this out the door quick to stay on top of the news cycle

▲▼ mathisfun12318:01 hn>

they're releasing this today because the pytorch conf is this week...

▲▼ parthdesai18:11 hn>

Why be rude on purpose? OP clearly prefaced by saying it was a dumb question

▲▼ geremiiah18:24 hn>

No, these are two very different objectives.

▲▼ 0x00cl00:49 hn>

We might never know, but they probably didn't read the news and started working to get this out, they were probably working on it for a while now.

Personally the question is if they are "saving" other projects or news so they can be released in case a competitor makes a move? Who knows if this was ready days or weeks ago and were waiting on someone to drop some news, so they can shadow those news.

▲▼ 23agt17:27 hn>

Google is selling TPU shovels via Cloud services and also physically to select partners. So this makes sense.

There will be an abundance of shovels. Nebius already crashed by almost half from its hype peak.

▲▼ airza17:33 hn>

it doesn't seem like there's an abundance of shovels coming anytime soon

▲▼ juleiie20:30 hn>

Shovels and gold aren’t the problem, humans are the problem

either AI achieves hyper-efficiency and triggers systematic economic demand destruction due to unemployment, or it underperforms and sparks a massive tech-sector asset bubble burst

If AI is as good as valuations - it crashes. If AI isn’t as good, it crashes. all eggs in one basket economy.

Every future leads to a massive financial shitstorm

AI is priced in as a technology to end all markets. The last bull market you will ever see.

It’s a miracle markets didn’t notice this “damned if you succeed damned if you don’t” type of inevitable checkmate

I have been building a bunker

─ 6 more ─
▲▼ tjwebbnorfolk22:52 hn>

Everyone says there's a massive compute shortage. But where is it showing up? For whom is there a shortage?

Every time I ask Claude to do something, it does it just fine. I never have to wait in any sort of queue that would be common in other kinds of shortages.

─ 8 more ─
▲▼ nelaggy17:50 hn>

so if the moat isn't the model and the moat isn't the inference layer, i guess the moat is the hardware now? what does this mean for frontier labs?

▲▼ JacobAsmuth17:57 hn>

Products can also be a moat.

▲▼ badrequest18:10 hn>

hardware has always been the moat in the AI space

▲▼ AndrewKemendo19:02 hn>

Will always be true

▲▼ AnotherGoodName19:15 hn>

Yeah a lot of people bought into the idea of CUDA being a moat but we’re well past the point where it’s pretty trivial to jump to another equivalent stack on the software side.

─ 5 more ─
▲▼ pcmoritz18:19 hn>

For people interested in this: I've been working on an open-source libtpu implementation for https://tenstorrent.com/ accelerators as a side project, it can already run most of torchtpu, see https://github.com/pcmoritz/libtt (based on the tenstorrent software stack). It shows all the things involved in lowering torch to tile based accelerators.

▲▼ yhjc269219:00 hn>

This is super cool!

▲▼ pcmoritz19:04 hn>

Thanks for the encouragement, if you have the hardware and end up trying it out I'd love to get your feedback (feel free to drop an issue in the repo) :)

─ 2 more ─
▲▼ asparagui19:03 hn>

Very cool! I have been using Lean to drive PJRT like so: https://github.com/brettkoonce/lean4-mlir and in theory your code could unlock another platform!

▲▼ pcmoritz19:07 hn>

Thanks for sharing, this is super cool! Right now my approach to correctness it to just run as many tests as possible and fix them (torchtpu greatly expands the amount of available tests), but formal verification is also super cool. Having a look at your book https://lean.brettkoonce.com/blueprint.pdf

The Tenstorrent ISA is documented btw https://github.com/tenstorrent/tt-isa-documentation, I wonder if one could do the verification end-to-end with the hardware.

▲▼ fancyfredbot18:22 hn>

Cool! XLA is pretty good + potentially a better compiler infrastructure than inductor which will lead to improved performance on all hardware.

Also I guess this is the final nail in the coffin of Tensorflow.

▲▼ ismailmaj19:19 hn>

Amazing news, I remember the days when you had to fight XLA to make PyTorch run on TPUs, it seems we finally got first-party support!

Since HW specifics live mostly in the kernel layer (Pallas or CUDA), I imagine the Jax vs PyTorch question is more of a style preference now?

▲▼ tuna7419:28 hn>

Is the Linux driver available?

▲▼ nico19:33 hn>

Pardon my ignorance, but who else besides Google has TPUs? Are they commercially available somewhere? What’s their main application right now outside of Google?

▲▼ cavisne19:44 hn>

You can rent them on cloud + they sell directly to Anthropic. Its pretty well known that Anthropic is a heavy user of TPU's (along with Trainium & GPU's)

▲▼ snake_doc01:20 hn>
▲▼ atty03:57 hn>

Google is selling TPUs to enterprise clients for on prem deployments. We’ve evaluated them but decided to stick with Nvidia, at least for one more generation. We’re a relatively large user of GCP.

▲▼ dalemhurley20:18 hn>

Google and Apple are going to move consumers and ordinary business users to edge inference. This is more disruptive to the upcoming IPOs than most investors understand.

▲▼ tjwebbnorfolk22:50 hn>

I would love to be able to buy a TPU for inference

─ 3 more ─
▲▼ emmelaich01:07 hn>

You can buy a Google Coral TPU, does that count?

─ 1 more ─
▲▼ anuptalwalkar23:24 hn>

I would love to see them move off into edge computing. There should be some autonomy and siloed experience in day to day usage.

▲▼ lofties01:03 hn>

Google, Apple, and don't forget our friends DeepSeek!

▲▼ villgax13:36 hn>

Yeah right, try generating an image on Apple Silicon or an Android phone with any of the Qwen or Flux family of models, let alone videos or prefill heavy LLMs.

▲▼ amelius22:41 hn>

Soon to be written by AI anyway, so they might as well release it now.

▲▼ saucesaft23:21 hn>

bad news for jax

▲▼ jax_bro23:54 hn>

not really!

▲▼ jart05:40 hn>

Let me guess, they gave you something better and it's eating you up inside? That's the way your hard-core Commie works.

─ 3 more ─
▲▼ frobisher06:31 hn>

Question: does this make JAX obsolete? I was having fun learning it!

▲▼ csvance12:08 hn>

It makes PyTorch work nicely on TPU, which is impressive mostly because of how unstructured PyTorch is with its conventions. From a compiler standpoint JAX is much easier to work with since its all pure functions. This means that JAX also has access to fairly cutting edge compiler tech like Enzyme which is quite relevant for scientific machine learning work.

▲▼ g5889288106:37 hn>

great! where can I buy a TPU?

▲▼ ranger_danger12:53 hn>

How about open-sourcing the proprietary blackbox Titan security chip, that you pinky-promised to open but never did?

▲▼ tingkuanpei12:58 hn>

Very interesting work. Google should have done this a long time ago. PyTorch's ecosystem is just so rich.