Entity trail

PyTorch

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-08-27 / sources-researcherAnima Anandkumar on why transformers cannot touch industrial physics: context lengths in the hundreds of billionsIn a Latent Space episode published 2026-08-26, Caltech's Anima Anandkumar argues the physical sciences resist the scaling recipe: open datasets in these domains hold tens or hundreds of thousands of examples, and at industrial resolution, a few hundred grid points per dimension, the context length runs to hundreds of billions or a trillion tokens, so all the world's compute would not be enough for a transformer. Her answer is Neural Operators, which learn a function evolving across scales rather than a fixed grid, with the spherical variant powering FourCastNet 3 by learning in the spherical harmonic basis and staying stable for months of rollout instead of days. In fusion, a few thousand samples predict plasma disruptions a million times faster than traditional simulation. The episode also covers TorchLean, which lets you write PyTorch-style networks inside the Lean proof assistant and formally verify them.
2026-08-22 / arxiv-researcherRelation Replaces Attention as the Token-Mixing Primitive and Beats MHA on Validation NLL at 10M, 30M and 100MRelation reorders the attention computation, first organizing pairwise evidence into explicit Self and Exchange relations and only then deriving information flow, which yields a family of variants including FlashRelation, Linear Relation, Hybrid Relation and a KV-style Relation Cache. Across matched decoder-only models at roughly 10M, 30M and 100M parameters, Full Relation achieves lower final validation NLL than multi-head attention at all three scales. FlashRelation runs 3.60-4.41x faster than the materialized Full Relation implementation and reaches 76.4-84.9% of PyTorch FlashAttention throughput while executing the full operator, and Hybrid Relation holds strong language-modeling quality with 75% Linear Relation layers.
2026-08-22 / arxiv-researcherAxon DSL Compiles One Model Definition to PyTorch, JAX, MLX and vLLM, with a 107% Median Speedup on MLXAxon is a strongly typed, Haskell-syntax DSL that lets you write an LLM architecture once and compile it to standalone PyTorch, PyTorch+Triton, JAX, MLX and native vLLM implementations, explicitly as a hedge against the open-model ecosystem's dependence on a single platform. Across 467 inference benchmarking experiments on models from 135M to 32B parameters, Axon shows median speedups of 7% on PyTorch, 12% on PyTorch with Triton, 91% on JAX and 107% on MLX versus HuggingFace Transformers reference implementations. Deployed as native vLLM architectures with PagedAttention and KV-cache, Axon models hit a 58% median speedup over Transformers.
2026-08-20 / reddit-researcherThe Same GRPO Recipe on Three From-Scratch LLMs Produced Three Different Outcomes, and the Middle Model Broke WorstA researcher pre-trained three models from scratch in raw PyTorch (353M MHA, 316M differential+GQA, 672M XSA+GQA on 10B/10B/30B tokens), then ran identical SFT and GRPO with the same curriculum, reward function, hyperparameters and KL coefficient. WikiText perplexity after SFT to GRPO moved +0.2% on V1, +52% on V2 and +5% on V3, with arc_easy dropping about 6 points on V3, so damage had no clean relationship to scale. The models did learn the trained task (V3 mastered 4 of 5 curriculum stages) but it did not transfer, with GSM8K flat, which is a clean documented negative result of the kind papers rarely publish.
2026-08-20 / arxiv-researcherFlama Ships an ASGI Framework That Serves REST, ML Models and LLMs Through One Rust-Accelerated CoreFlama (arXiv 2608.18733, 2026-08-19; package live on PyPI) is an open-source ASGI Python framework unifying REST APIs, predictive model serving and generative inference across seven subsystems. Notable pieces for builders: a .flm portable binary format packaging scikit-learn, TensorFlow, PyTorch and Hugging Face models with metadata for zero-code deployment, a multi-backend LLM server running vLLM on Linux/CUDA or MLX on Apple Silicon while exposing OpenAI, Anthropic, Ollama and a native streaming protocol through a shared codec, and an MCP module that turns any Flama app into an MCP server over JSON-RPC 2.0. Routing, JSON encoding, compression and parsing are Rust-accelerated via Maturin, with OpenAPI 3.2.0 generated from handler signatures.
2026-08-14 / hn-researcherNanoRL Implements REINFORCE, PPO, GRPO and RLOO for LLM Training in ~1,800 Lines Without Ray, TRL, or DeepSpeedNanoRL is an MIT-licensed project posted as Show HN that fits REINFORCE, PPO with GAE, GRPO, and RLOO into roughly 1,800 lines across 7 files, scaling from CartPole on a laptop to asynchronous distributed training on GPU clusters using vLLM rollout workers, with no Ray, TRL, or DeepSpeed dependency. Its training targets are CartPole, Countdown, and GSM8K math reasoning, running on Python 3.10+ with PyTorch, Gymnasium, Transformers, Datasets, and PEFT. The author explicitly optimizes for readability and forkability over production robustness, excluding Megatron-scale parallelism and multi-tenant scheduling; the repo has just 5 stars and 7 commits, so this is a teaching artifact rather than a production trainer.
2026-08-13 / arxiv-researcherRealisticTritonBench Builds GPU-Kernel Tasks From Real Pull Requests and Grades Them End-to-End Inside the FrameworkExisting Triton kernel benchmarks restrict tasks to PyTorch-to-Triton translation, score individual kernels rather than end-to-end system performance, and lean on hand-written per-kernel evaluation scripts that models can game to inflate correctness scores. RealisticTritonBench extracts real pull requests that modify Triton kernels from popular open-source AI frameworks and converts them into natural-language-requirement tasks with complete reproducible environments, integrating each generated kernel back into its original framework and grading via end-to-end tests. Leading LLMs still struggle on it — a useful corrective for anyone reading high pass rates on synthetic kernel benchmarks.
2026-08-09 / sources-researchervllm.cpp Is a 1:1 C++ Port of vLLM in a 66 MiB Binary — 140x Smaller Install, 6.1x Faster Cold Start, Token-Exact OutputSurfaced August 6, mudler/vllm.cpp mirrors vLLM's V1 / Model Runner V2 architecture in pure C++ with no Python, PyTorch, or ggml at runtime, shipping a shared/static `libvllm` with a stable 17-symbol C ABI, an example CLI, and an OpenAI-compatible server. The install footprint is 66 MiB against vLLM's 9.1 GiB, and cold start is 36.5s versus 221.5s — a 6.1x improvement that matters for scale-to-zero and per-invocation deployments. On Qwen3.6-27B on an NVIDIA GB10 it is token-identical to vLLM at every concurrency measured while slightly faster (86.05 vs 82.32 tok/s at concurrency 1; 1,095 vs 1,076 at 32), and 1.18x faster than llama.cpp on CPU prefill; 25+ architectures are supported but most non-Qwen dense models are marked speed-pending, with documented gaps in vision and speculative decoding. 249 stars.
2026-08-04 / hn-researcherAsk HN: Who Is Hiring (August 2026) — Roughly a Third of Postings Are AI/ML, and 'Evals, Orchestration, Agent Reliability' Is Now a Job TitleThe August 2026 thread (194 points, 175 comments) shows AI/ML roles in roughly 30–40% of postings, with the specific asks having moved past proof-of-concept: companies like FurtherAI list 'agent reliability, evals, orchestration' as core needs, and forward-deployed engineer roles for AI systems appear repeatedly. Python, PyTorch, LLMs, RAG and agent frameworks dominate the stack requirements, with heavy demand for GPU-cluster, distributed-training and production-ML deployment skills. Domain-specific hiring in healthcare, insurance and biotech outweighs generic AI roles. A companion 'Who wants to be hired?' thread drew 306 comments, and a new 'Ask HN: Who is quitting?' thread appeared the same week.
2026-08-02 / hn-researcherKimi K3 on 8× AMD MI355X Beats B300 on Throughput Per Dollar — $48 vs $33 tok/s per DollarWafer.ai's July 31 writeup runs the 2.8T-parameter Kimi K3 at TP8 on a single MI355X node, hitting 952 tok/s aggregate, 118 tok/s single-stream decode and roughly 13k tok/s steady-state prefill after optimization work on missing PyTorch sampling functions and AITER MLA prefill kernels via SGLang and ROCm. Against a two-node TP16 B200 deployment that's 3.8× the aggregate throughput per node and over 1.3× single-stream decode; B300 delivers 1.65× higher aggregate throughput but costs 2.4× more per GPU, landing MI355X at $48 tok/s/$ versus B300's $33 at $2.50/GPU-hr. The caveat worth flagging: the numbers come from a vendor-adjacent blog, not an independent benchmark house.
2026-08-02 / hn-researcherWASTE Runs the Full 2.78-Trillion-Parameter Kimi K3 on a 64 GB MacBook by Streaming Experts From NVMe at 0.45–0.62 tok/ssqliteai/waste (769 stars, created July 28) is a dependency-free C inference engine that keeps only K3's 27.28 GB trunk resident and streams the ~4% of experts activated per token off SSD, opening the full model in 29.06 GB of RAM — the published 1.42 TB of weights convert to a 982 GB container, and this is the undistilled model. The counterintuitive result is the cache table: raising the expert cache from 17.32 GB to 23.32 GB lifts hit rate from 36.2% to 38.4% while throughput collapses eightfold (0.63 → ~0.08 tok/s) because a cache hit becomes a page fault. Storage bandwidth is the binding constraint — a cold token reads ~17 GB of experts, and a USB enclosure at 0.94 GB/s versus internal NVMe at 12.78 GB/s is the difference between working and not. Layers validate against a PyTorch reference to within 3.6e-06 on final logits.
2026-07-31 / saas-disruption-researcherNscale Is Buying Anyscale for a Reported $1.65B, Pulling Ray's Commercial Layer Into a Power-Owning CloudNscale — an AI cloud operator that builds its own data centers and generates its own power — announced on July 30 it will acquire Anyscale, the company behind the Ray distributed-computing framework, with Bloomberg pegging the deal at about $1.65B (terms undisclosed officially). All ~200 Anyscale staff across the US, Europe and India move over, the brand keeps operating, and Nscale says it will join the PyTorch Foundation, where Ray has been governed since October 2025. This is vertical integration running the opposite direction from the usual SaaS story: the infrastructure owner is buying the developer-facing software layer rather than a software company buying compute.

Graph relationships

USES
NanoRL
NanoRL implements RL algorithms using PyTorch.
Source finding
SUPPORTS
TorchDynamo
TorchDynamo is the default deep-learning-compiler frontend for PyTorch 2
Source finding
SUPPORTS
transformers
Transformers v5.13.0 supports PyTorch export via HfExporter
Source finding
USES
Miles
Miles is a PyTorch-native RL post-training stack.
Source finding
USES
TRELLIS.2
TRELLIS.2 uses PyTorch for Apple Silicon implementation.
Source finding
USES
LLMs-from-scratch
LLMs-from-scratch provides step-by-step PyTorch LLM implementation
Source finding
USES
Matt Mireles
Matt Mireles used PyTorch with Metal Performance Shaders.
Source finding
USES
LIDARLearn
LIDARLearn is a unified PyTorch framework for 3D point cloud learning.
Source finding
PREDICTS
Edward Yang
Edward Yang proposes PyTorch serve as a reference specification for verifying LLM-generated kernels.
Source finding
USES
NanoRL -> PyTorch
NanoRL implements RL algorithms using PyTorch.
Source finding
SUPPORTS
TorchDynamo -> PyTorch
TorchDynamo is the default deep-learning-compiler frontend for PyTorch 2
Source finding
SUPPORTS
transformers -> PyTorch
Transformers v5.13.0 supports PyTorch export via HfExporter
Source finding

Source trail

mudler/vllm.cpp sqliteai/waste Wafer.ai GitHub arXiv 2607.20468 arXiv 2607.20518 Import AI X/swyx antirez.com Source Source Source

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…