Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

.CapIX Dev's vision is to bring quantum computing to retail The three layers underneath: - Layer 1: GPU mesh aggregating Surplus Intelligence, Pod the Squire, OpenRouter - Layer 2: Smart router (heavy tasks go to the GPU, light tasks go to the CPU, quantum computing in the future?) -...

13,184 Aufrufe • vor 2 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

The teams shipping AI agents right now are bleeding money on the dumbest possible expense: teaching a 400B-parameter model to read a file name. Every time an AI agent needs to "see" something today, it routes an image through a frontier model. OCR, object detection, checking if a button exists on screen. You're paying GPT-4o or Claude pricing for tasks that require perception, not reasoning. One agent workflow processing a few thousand screenshots per day can burn through more on vision calls than on the actual thinking. Perceptron's Isaac is 2B parameters. Built by the team that created Meta's Chameleon multimodal models. On perceptive benchmarks, it matches or beats models 50x its size. The VQA, OCR, and object detection scores are competitive with models running on infrastructure that costs orders of magnitude more. The MCP wrapper is the distribution play. One install command and every Claude Code agent can offload vision tasks to a model that runs on a single consumer GPU. The agent keeps its reasoning in the frontier model and routes perception to a specialist. That split is how you get vision-heavy agent workflows from "technically possible but expensive" to "cheap enough to run on everything." This is the same pattern that won in every other compute-intensive stack. General-purpose handles orchestration. Specialists handle the heavy lifting. Graphics went through it. Audio went through it. Video encoding went through it. Vision in AI agents is next. The teams building agents that see 10,000 images a day will care about this before anyone else does.

Aakash Gupta

55,978 Aufrufe • vor 5 Monaten

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.

kocer

29,945 Aufrufe • vor 5 Tagen

Cathie Wood just flagged the sleeper trade inside the AI boom that most people are completely missing. Everyone has been chasing GPUs. Nvidia, the data center buildout, the chip arms race. That trade has been obvious for two years. But OpenAI's CFO Sarah Fryer said something quite different: people are going to be really shocked by how agentic AI activates CPUs. Right now, for every CPU in an AI workload, there are 4 to 5 GPUs. That's the current ratio. Wood thinks that ratio is going to 1 to 1. Think about what that means. AI inference at scale, agents running autonomously, pipelines executing tasks across systems. The compute mix shifts dramatically away from pure GPU dominance. CPUs become a first-class citizen in the AI stack. Cathie called it going "back to the future." Intel has taken off. Flex (formerly Flextronics) is booming. Stocks that were giants in the dot-com bubble are resurging because the underlying demand for their products is real again. The GPU trade made sense at the training stage. You need massive parallel compute to train frontier models. But agentic AI runs differently. Agents are constantly orchestrating, reasoning, calling APIs, executing workflows. That workload looks a lot more like traditional computing. And traditional computing runs on CPUs. If Cathie Wood is right about the ratio collapsing to 1:1, the CPU demand signal embedded in the AI buildout is orders of magnitude larger than the market is currently pricing.

Milk Road AI

234,897 Aufrufe • vor 3 Monaten

UC Berkeley just open-sourced FreeToken. (2–4x faster local LLM inference than Ollama) the results are wild: - Qwen3.6-35B on an 8GB GPU at 39.3 tokens/s - DeepSeek-V4-Flash 284B on a 32GB GPU at 22 tokens/s - GLM-5.2 753B on a 96GB GPU at 14.9 tokens/s a 35B model at 16-bit precision needs about 70GB just for its weights. even at 4 bits it is close to 18GB, and FreeToken serves it on an 8GB GPU. let me explain how: all three models mentioned above are Mixture-of-Experts, and that is what FreeToken takes advantage of. each layer holds hundreds of separate experts plus a small router that picks a few of them per token. Qwen3.6-35B activates roughly 3B of its 35B parameters per token. DeepSeek-V4-Flash picks 6 of 256 experts per layer, so 13B of its 284B run at a time. so compute was never the bottleneck. the weights a single step touches fit comfortably on a consumer GPU. every expert the router might pick still has to exist somewhere. they sit in system RAM, and the GPU keeps a cache of the ones the model has been using recently. so everything comes down to what happens when the router picks an expert that is not on the GPU. there are two ways to serve that miss: 1. copy it over PCIe and run it on the GPU 2. run it on the CPU, where it already lives both read from the same system memory, so they compete for one pool of bandwidth instead of adding to each other. existing engines pick one option and freeze it when the model loads. but routing changes on every token, so a fixed choice misses most of what the model asks for. FreeToken measures both bandwidths on your machine and splits each step's misses between the two paths in proportion. the GPU and CPU results then merge exactly, with no approximation. two machines with the same GPU can end up wanting opposite strategies, which I did not expect. a 5090 in a gaming desktop should push nearly everything over PCIe, while an 8GB laptop is better off computing most misses on the CPU. none of that is readable off a spec sheet, so the engine profiles it once per machine. the second half of the design is about agents. coding agents constantly rewrite their own history, and every edit normally forces thousands of tokens back through prefill. FreeToken saves its checkpoints at the exact boundaries agent frameworks cut on, so it only reprocesses the new part. its slowest first token stays under 44 seconds, while llama.cpp peaks at 232 and KTransformers at 946. it serves the OpenAI and Anthropic APIs under Apache 2.0, so Claude Code and Codex can point at it directly. releasing weights publicly decides who can download a model, not who can afford to run one. frontier open models keep shipping, and running them still assumes a rented cluster. meanwhile there are over a hundred million consumer machines with discrete GPUs sitting mostly idle. closing that gap was never a hardware problem, and work like this is what turns open weights into something you can actually use. paper: repo: almost every idea in this post, from why memory bandwidth decides the outcome to why moving weights costs more than computing on them, comes straight out of how a GPU is built. I wrote a detailed primer on that. the article is quoted below.

Akshay 🚀

338,326 Aufrufe • vor 13 Tagen

This is why Nebius will be a trillion dollar hyperscaler (Save this). Nebius is not building another GPU rental shop but rather building a vertically integrated hyperscaler that owns everything from the physical data center, to the server rack hardware it designs in house, to the software stack, to the inference delivery layer. Nearly every other neocloud is essentially a reseller of someone else's infrastructure but Nebius owns the full stack end to end and that distinction is the entire thesis. Here is why vertical integration is the winning architecture for the inference era. AWS and Azure were architected for general purpose computing and every AI workload they run sits on top of infrastructure that was never designed for it, patched, adapted and optimized after the fact. Nebius was built from day one specifically for AI which means every layer of the stack is purpose built and co optimized. The rack design, the networking topology, the cooling systems and the software that orchestrates it all are engineered together as a single system rather than assembled from parts that were never meant to work together. That architectural difference compounds with every passing quarter as AI workloads grow more complex and the performance gap between purpose built and general purpose infrastructure widens. The software layer is where the real competitive moat lives. Most infrastructure companies think of software as a wrapper around hardware while Nebius thinks of software as the product with hardware as the substrate it controls. The company is building an AI native cloud platform where the software layer handles model serving, inference optimization, fine tuning pipelines and developer tooling as first-class primitives. This matters because inference efficiency is almost entirely a software problem. Two companies running identical GPUs can deliver dramatically different performance and cost per token depending on how intelligently the software schedules, batches and routes inference requests across the cluster. Nebius is also building for a fundamental shift in how AI infrastructure gets consumed. Today, enterprise developers navigate massive cloud service catalogs spinning up clusters, managing configurations and building deep expertise in AWS or GCP-specific tooling. The next generation of builders will simply provision agents to interface with infrastructure directly. Nebius is architecting its software layer for that future , one where the interface between the developer and the compute abstraction layer looks nothing like what AWS built in 2006. The entire available capacity has been sold out every quarter. And that is the best possible validation that what Nebius is building is exactly what the market needs and that the market is willing to commit at a scale that makes the current valuation look like the beginning of a much longer story. Long Nebius and make sure to follow me Melvin for more overlooked AI stocks.

Melvin

34,306 Aufrufe • vor 1 Monat