posts · 2026-07-23

The reason to click: it changes how document parsing generates output. Traditional models decode token by token — the longer the page, the slower it gets. HPD-Parsing uses one main branch to understand the full layout, then dispatches each region to parallel branches that generate simultaneously, with each branch predicting multiple tokens per step. Result: 4,752 TPS peak, 1.62× the previous fastest parser and 3.06× its own autoregressive baseline. Accuracy didn't tank either — 94.91% on OmniDocBench v1.6, currently the top score among end-to-end unified parsers. The staged adaptation with automated difficulty-aware data curation seems to have patched the accuracy drop from switching to parallel decoding. Where I'd discount it: the post doesn't disclose hardware specs or VRAM. 4,752 TPS is a peak number — real throughput and latency depend on your setup. OmniDocBench is also English-document-focused, so mixed-language or Chinese-heavy layouts are untested here. If it runs close to claimed speeds in your environment, document parsing API costs could drop noticeably.

The Reddit headline is what grabs you: cheaper than DeepSeek V4 Flash, better than V4 Pro. Poolside is a Western neolab, and their model is roughly 10x smaller than Thinking Machines while competitive on code benchmarks. The post doesn't give exact pricing or latency—you'll need to dig into their tech report and the Latent Space podcast episode for the breakdown. I'd discount the Reddit framing a bit since comparison baselines are rarely apples-to-apples, but if the efficiency claims hold, this is a real signal for teams paying per token.

This caught my eye because Beijing just put several industry buzzwords into formal policy: Harness Engineering (the infra layer that governs agent behavior and safety), Token Economy, and OPC (one-person company). The core shift is moving billing from token consumption to value-based pricing, while pushing three service models—TaaS, AaaS, RaaS—with agents landing in phones, glasses, and cars. But the post is just a ten-point direction list. No subsidy amounts, no timeline, no pilot names. I'd read this as Beijing staking a claim on defining the agent industry, but it's still several steps away from actual money moving.

This one's worth opening because Poolside turned "small team, fast cycles" into a reproducible engineering pipeline. They run 10–20K experiments a month, ship from pre-training to release in 5–8 weeks, and their new Laguna S 2.1 — a 118B-total, 8B-active MoE with a 1M context window and dual thinking modes — beats Thinking Machines' ~1T open-weights model on benchmarks. Eiso made a few sharp claims on the pod: MCP and traditional tool calls are "stupid," RL will move earlier into pre-training, and 95% of model gains come from better data or compute efficiency. Those are opinionated, but they're backed by two years of actually running a model factory. Where I'd discount a bit: the benchmark comparisons shown are mostly against Thinking Machines' ~1T model. We don't yet see head-to-head numbers against other MoE peers like Qwen 3.5 MoE or DeepSeek V4 Pro. And the post doesn't give latency or throughput figures for the 8B-active setup on real code tasks — third-party benchmarks will tell us more about the actual dev experience. One thing that's genuinely hard to ignore: fewer than 70 researchers, a $500M raise, and they're shipping open weights with detailed tech reports. Eiso said he'd rather live in a world with 100 foundation model companies than five — coming from someone running one of those companies, that lands differently than a VC saying it.

This post caught my eye because it's a concrete budget build: four used 20GB RTX 3080s, an X99 board with CPU and 64GB RAM, totaling around $2,000. With MTP on, decode hit 69 tokens per second near 256K context on Qwen3.6-27B — faster than a quad 5060 Ti setup. I'd discount the claim a bit. The post doesn't share any code accuracy benchmarks, just speed numbers. The "high accuracy" part is the author's trust in Qwen3.6, not a measured result. Also, the test ran on rented Vast AI instances with power-capped cards, so your own build might not match exactly. If the numbers hold, the useful bit is the cost math: $400 per 3080 20GB is way cheaper than new cards, and 80GB total VRAM fits a lightly quantized 27B dense model comfortably. For anyone building a local code assistant and tired of API bills, this combo is worth running your own numbers on.

This post caught my eye because it lowers the bar for multi-GPU inference to almost nothing. A Reddit user connected two PCs with three RTX 4060s using a plain Ethernet cable and ran the 39.7 GB laguna Q2_K_XL model. On an 11k-token prompt with ubatch 768, generation hit 28.28 tok/s, and network traffic peaked at just 30–70 MB/s — nowhere near saturating a gigabit link. I'd discount it a bit: the post doesn't include a single-machine dual-GPU baseline for the same model, so we can't tell how much speed the second node actually costs. Also, three 4060s total 24 GB VRAM while the model is 39.7 GB, so it's clearly spilling into system RAM — the real bottleneck might be PCIe bandwidth, not the network. Still, the direction is solid. If you've got two old machines lying around, a $20 cable can pool their VRAM to run models that wouldn't fit on either one alone. No switch, no InfiniBand. For the local LLM crowd, that's a genuinely useful reference point.

The speed numbers are what make this worth a click: 13 seconds for a 5-second 720p clip on a single H100, 120x faster than Wan 2.2-A14B. The trick is swapping 75% of standard quadratic attention for gated linear attention that scales linearly with sequence length, then dropping in periodic softmax anchors to restore global token interactions. The 5B model hits VBench 84.30, competitive with much larger full-attention DiTs. I'd discount this a bit—no open-source commitment, no training data details, and VBench isn't great at separating motion quality or physical consistency. But if you're trying to generate long videos on a single GPU, this hybrid approach is genuinely useful: it's not about pushing quality ceilings, it's about getting latency down to something usable. The Sol-Engine compilation stack squeezing out another 3.58x speedup suggests the architecture is hardware-friendly from the ground up.

This piece is worth your time because it dissects a hype flywheel in real time. It started with a 12-word joke tweet by Peter Steinberger—zero specs, zero code. Within 72 hours, control-flow folks rebranded DAG orchestration as a new paradigm, influencers spun it into 'virtual company org charts,' Eigent AI injected 'governance graphs' to sell their platform, and others confused it with knowledge-graph RAG. Anthropic has called these structures Workflows since 2024 and still does. Production numbers tell the real story: multi-agent systems burn 15× the tokens of normal chat, coordination failure rates hit 41–86.7%, and single-agent runs on the same topology perform comparably at far lower cost. I'd bookmark this as a hype-deconstruction manual—next time a buzzword explodes, ask whether anything actually changed under the hood.