Posts

Featured Post

Special Edition: Jev and Its Impact

Image
  What happens to the token economy when a model stops writing and starts deciding Copyright: Sanjay Basu There is a particular kind of Sunday morning that begins with two small silver boxes humming on a desk and a question. A question I am asking myself now. If the whole industry has spent three years learning to pay for tokens the way we once paid for long distance calls, priced by the minute and rationed accordingly, what happens the moment a model arrives that does not bill you for the talking at all. That was the week Jev showed up in my sandbox, and it rearranged more furniture than I expected. Let me set the scene honestly, because the setup matters as much as the model. I had two NVIDIA DGX Spark units on the bench, each carrying a GB10 and 128GB of unified memory, joined by a single QSFP cable with no switch in the middle. NVIDIA Sync did the introductions, walked the ConnectX-7 topology, planned the addresses, and exchanged keys over the fabric while I made coffee. Two hu...
Post a Comment
Read more

Installing Jev on a Two-Node DGX Spark Cluster

Image
  A TECHNOCRAT'S DISCERNMENT  ·  BUILD LOG A hands-on setup guide. Nemotron as the generator, Jev as the decision layer, TypeScript holding it together. This is the guide I wish I had on Saturday morning. We are going to stand up two NVIDIA DGX Spark units as a single cluster, serve a Nemotron model across both of them as the heavy generator, and then put Jev in front as the fast decision layer that decides what the generator ever has to see. One box would work for a smaller model. Two boxes, joined by a single cable, give us 256 GB of unified memory and the room to run a real generator at home. One point worth stating up front, because it changes how you read every step below. Nemotron runs locally on your cluster. Jev does not. Jev is TypeSafe AI's hosted System One model, and you reach it over HTTPS through the jev-code CLI or the TypeSafe SDK. So what you are installing on the cluster is the local generator, the Jev client, and the TypeScript harness that wires the t...
Post a Comment
Read more

Cost per token, not cost per watt

Image
  Copyright: Sanjay Basu There is a particular kind of electricity in a hall where people have stopped debating whether the future is arriving and started arguing, in earnest, about how to build it. That was the AI Infra Summit this year. Every theater, main stage, wrokshop rooms, I walked past was standing-room. Laptops open on knees, phones lifted to catch a slide, the quiet hum of a few thousand people who all came to solve the same problem from slightly different angles. The expo floor sprawled shoulder to shoulder. Booths two and three deep, demos running non-stop, the aisles of Hall B a slow river of badges. And the best part of an industry this large and this fast is that it still feels small in the ways that matter. I could barely cross the floor without running into someone I’ve built with, argued with, or learned from over the last three decades. I met current and old colleagues from Oracle, AWS, EMC, Dell, HP, IBM, and a dozen startups that didn’t exist eighteen months a...
Post a Comment
Read more