
Founding Chip Architect, @river_ai_inc Fmr AWS Tranium, Tesla Dojo, CPUs (x86+ARM). PhD Computer Arithmetic
Joined December 2022
- Tweets621
- Following474
- Followers2.7K
- Likes2.1K
Eric Quinnell retweeted
Introducing River Recipes: our open-source initiative for turning promising research into vetted, reproducible training recipes.
Our first recipe tackles text-to-SQL, where our trained open models beat GPT-6 Astra Pro and Claude Opus 5.5 on Arcwise-Plat for less than 1% of the cost.
Read the full breakdown and explore the recipe ↓
river.ai/achieving-frontier-…
Eric Quinnell retweeted
It's beneficial for a software engineer to learn chip design so they understand how numerics flow through circuitry each cycle.
Eric Quinnell retweeted
The River API was tested in this blog post and outperformed Tinker on reinforcement learning runs with identical training code. We spent a lot of effort to get details like routing replay right so you get the best possible results with the API.
Eric Quinnell retweeted
Excited to share I've joined @river_ai_inc to work on personal AI!
As AI products become pervasive in everyday life, it's clear this technology needs to be private & owned by the users. I'm looking forward to a future with great products and alternatives to centralization.
Eric Quinnell retweeted
Today, we're sharing that River AI has raised $1.1 billion, led by @generalcatalyst and @amppublic with strategic investment from @nvidia and @AMD. Additional investors include @ycombinator and @Temasek.
We imagine a future where your AI works entirely for you and deeply aligns with your values. Compared to the corporate chatbots of today, it will feel completely different: responsible, curious, and truly yours. Most importantly, you'll own everything: the hardware it runs on, the data it learns from, and the intelligence itself.
Our training API is already live and powering incredible work today. This new funding accelerates our push to bring the full personal AI stack to life.
Read River AI CEO Igor Babuschkin’s (@ibab) conversation with the New York Times to learn more: nytimes.com/2026/08/11/techn…
Eric Quinnell retweeted
River API is now available to everyone.
Fine-tune and run RL on frontier open models. Fast, cheap, and scalable.
Go to console.river.ai/ to try it out!
Eric Quinnell retweeted
First you have to understand that modern LLM inference already disaggregates weights as models outgrew single chips years ago. You shard either by layer (pipeline parallelism) or by slicing every layer (tensor parallelism), and the two do very different things.
As an example, let’s look at Llama 3.3. It has 70B of weights and at FP8 that’s 70 GB of memory which is enough to fit on a single H100. Now that H100 has 3.35 TB/s of HBM, so the fastest it can ever decode for one user is 70/3.35 ≈ 21 ms/token or ~48 tok/s while using under 1% of its FLOPs. Now if we pipeline it across 8 chips: each chip holds ~8.75 GB, which means it only needs 1/8th the bandwidth and 1/8th the FLOPs to sustain the same aggregate throughput. Now crucially the token/sec a user gets is limited by the amount of data that crosses the link. In current LLMs all that is a small amount of activations for LLama 3.3 it’s ~8 KB per token….
Yes, you read that right it’s 8 KILOBYTES we are sending over a <900 GB/s link. That’s only 9 ns of serialization time but the overhead of 224G PAM4 SerDes adds ~100 ns per link traversal with RS-FEC which is 11x longer than the payload itself. And then you have the NVSwitch adding ~300 ns per hop and you need to pay twice. That’s ~600 ns of just hardware latency wrapped around 9 ns of data making a 98% tax before software even shows up. Then NCCL’s collective stack turns 600 ns into 10-20+ us… all to move 8 kilobytes lol. For comparison 8 KB serializes over 10 Gigabit Ethernet NRZ, in just 6.6 us. Pipeline parallelism however doesn’t make a single user faster as the token still needs to visit every layer in the sequence, so per-user speed is still weights / per-chip bandwidth.
To get more speed per user token you need to use tensor parallelism and have all the chips work on the same layer simultaneously. TP costs you 2 all reduce OPs per layer, 160 per token on llama 3, that’s still kilobytes of traffic but with NVLink overhead it’s a massive tax and why pipeline parallelism on most models still gives more interactivity per user. However, this gives you a huge latency lever to pull that scales tokens per second with interconnect speed instead of memory BW.
The clever amongst you might have also realized that sharding doesn’t just cut memory bandwidth per chip it also cuts FLOPs per chip and is why we have such bad MFU on decode. So once you’ve sized the link for the memory, you need to size the compute for it too. This is called “balancing the pipeline”, and currently no shipping chip does it because they were all designed as standalone monsters. Remember Tokens/sec = ~aggregate memory BW / bytes touched per token. At batch 64 in FP4 you need ~250 FLOPs per byte, and Blackwell ships 1,250. Provisioned 5x more than the narrow pipe of HBM. Nobody saturates shit cause they are all building around HBM.
So now it all comes full circle. Parallelism reduces memory bw pressure and thus FLOPs but increases interconnect latency pressure. Despite having HBM and GigaSERDES we aren’t actually doing more work lol. But if you really wanted to balance the pipeline you need to match the memory bandwidth, the flops, and most importantly the interconnect.
So what does that look like ? Well if you build around LPDDR’s lower bandwidth, lower your interconnect latency, you actually can beat Nvidia on decode with a fraction of the silicon.
Eric Quinnell retweeted
Sign up for the River API if you want to try it out. We’re open ing up access incrementally.
Eric Quinnell retweeted
i believe it was @divBy_zero that wisely said that, contrary to common sense, it is always easier to fix performance problems in silicon than change an entrenched sw stack
Hello, Moon. It’s great to be back.
Here’s a taste of what the Artemis II astronauts photographed during their flight around the Moon. Check out more photos from the mission: nasa.gov/artemis-ii-multimed…
Eric Quinnell retweeted
ahahahahahahahaahhaahahahahahaha okay you guys were right this hardware shit is hard.
Eric Quinnell retweeted
ml infra is really hard. great job to everyone who worked on the debug and writeup.
Replying to @claudeai
In our investigation, we uncovered three separate bugs. They were partly overlapping, making diagnosis even trickier.
We've now resolved all three bugs and written a technical report on what happened, which you can find here: anthropic.com/engineering/a-…
Eric Quinnell retweeted
some of yall need to realize that the last microprocessor that supported nibble-addressing was the intel 4004
which was also the first microprocessor in many respects
Eric Quinnell retweeted
Two things pose an existential risk to humanity: Superintelligent AI and human stupidity; and I’m not so sure about the AI
Eric Quinnell retweeted
Replying to @venturetwins
Listen. Strange women lying in ponds distributing swords is no basis for a system of government. Supreme executive power derives from a mandate from the masses, not from some farcical aquatic ceremony.
Eric Quinnell retweeted
Flew out to Amazon today to interview some AWS L3 SWE about an ec2 instance that they say has attained enlightenment.
Hearing some fascinating stories and being shown some mind blowing things.
The world is a magical place.




























