Building a "Subconscious Accelerator" for LLM Agents: VPU in Practice on Intel Iris Xe

VPU uses low-rank quantum-inspired evolution on integrated graphics to achieve 3000 FPS parallel exploration as a 'subconscious accelerator' for LLM agents.
The article introduces VPU v10.13, built by developer logout2login—a high-dimensional parallel evolution engine running on an ordinary Intel Iris Xe integrated GPU, operating on a low-rank approximation of a Hermitian Hamiltonian, evolving states via RK4 integration and measuring convergence with von Neumann entropy. Its P4-series lazy H_eff optimizations push latency down to 0.32ms, hitting 3000+ equivalent FPS at dim=512. VPU is wrapped as a LangChain tool for the Hermes agent, forming a complementary 'LLM serial thinking + VPU parallel exploration' architecture. Code is MIT-licensed.
LLMs infer token by token in serial. When they hit problems that require simultaneously exploring tens of thousands of paths at once—game tree search, multi-branch logical reasoning, high-dimensional state evolution—they fall short. Developer logout2login built VPU v10.13 (Vector Processing Unit), a high-dimensional parallel evolution engine that runs on an ordinary Intel Iris Xe integrated GPU, hitting 3000+ equivalent FPS at 512 dimensions and plugging into LLM agents via LangChain tool calling. In the author's words: "The LLM does serial thinking, the VPU does parallel exploration—together they form a 'subconscious accelerator.'" The code is open-sourced on GitHub under the MIT license.

The Problem: Serial LLMs Can't Explore in Parallel
Ask an LLM to solve a complex game theory problem, and it generates one step of reasoning at a time. If it goes down the wrong path, it either backtracks or prays its early judgment was correct. It has no mechanism to simultaneously explore 10,000 parallel paths and converge on the optimal solution.
VPU's approach is to run quantum-inspired state evolution on a low-rank approximation of a Hermitian Hamiltonian matrix: represent the problem space as a high-dimensional state vector σ∈[0,1]^dim, evolve the effective Hamiltonian H_eff using RK4 numerical integration, keep computation tractable via low-rank approximation (rank r much smaller than dim), and finally measure convergence using von Neumann entropy—the lower the entropy, the closer the system is to converging on a solution. Essentially it's like simulated annealing, but running at video game frame rates.
RK4 (fourth-order Runge-Kutta) is a classic numerical integration method for solving ordinary differential equations. It estimates the next state by combining four slope samples (k1, k2, k3, k4) within the current step, achieving fourth-order accuracy. Compared to Euler's method, RK4 has significantly smaller error at the same step size, at the cost of requiring four function evaluations per step. In VPU, the evolution of the state vector σ over time can be written as dσ/dt = f(σ, H_eff), and RK4 discretizes this continuous evolution into stable iterative steps. Since each step requires four calls to Hamiltonian-related operations, the computational cost of H_eff gets multiplied by four—which is precisely why the P4-series optimizations (especially P4a lightweight step skipping) yield such enormous gains.
Von Neumann entropy was originally used in quantum mechanics to measure the mixedness of a density matrix, defined as S = -Tr(ρ·ln ρ), ranging from 0 (pure state, fully determined) to a maximum proportional to the dimension (fully mixed). In VPU, the evolved state is mapped into a density-matrix-like object, and the entropy value becomes a measure of "degree of convergence": lower entropy means probability mass is concentrated on fewer states, and the system is closer to converging on a definite solution; high entropy means it's still diffusely exploring across multiple paths. It corresponds to "temperature" in simulated annealing, so entropy can also be used as a reward signal for subsequent VPU-in-the-loop training.
Four-Layer Architecture
Layer 1: VPU Engine (Python + NumPy + MKL)
The core engine StreamingVPU_v1013 maintains a low-rank subspace of the full dim-dimensional space. Each call to stream_tick() evolves one step, with the heavy lifting done by RK4Engine with pre-allocated buffers. All buffers are allocated once at initialization—zero malloc/free per step.
Layer 2: P4 Lazy H_eff Optimization—The Key Breakthrough
The four optimizations introduced in v10.13 (P4a–P4d) are the core of the entire performance leap:
| Optimization | Function | Effect |
|---|---|---|
| P4a | Lightweight steps skip H_eff computation | Eliminates 63% memory bandwidth bottleneck |
| P4b | Cache J_low/M_low when U unchanged | Saves 2 GEMMs per basis reuse |
| P4c | Pre-allocate RK4 buffers | Eliminates ~20 malloc/free per step |
| P4d | Auto-detect H_env changes via pointer ID | Guarantees correctness without manual triggering |
The result: lightweight steps (RK4 only) take 0.05–0.07ms, and even with full basis transformation added, average latency is only 0.32ms.
Low-rank approximation means approximating an original matrix using a decomposition with rank r much smaller than the original matrix dimension dim, typically in the form H_eff ≈ U · M · U^T (where U is a dim×r orthogonal basis and M is an r×r small matrix). Since the cost of matrix multiplication and evolution grows roughly linearly—or better—with rank, reducing rank from dim to 25 cuts per-step computation by one to two orders of magnitude, while the effective degrees of freedom of the Hamiltonian tend to be concentrated in a few principal subspaces anyway, so accuracy loss is minimal. Here U is the basis of the low-rank subspace, and "basis transformation" refers to recomputing U and its related matrices when the subspace drifts. P4b exploits exactly this: when U hasn't changed, J_low/M_low caches can be reused, saving two GEMMs (general matrix multiplications).
GEMM and MKL: GEMM (General Matrix Multiply) is the core BLAS routine computing C=αAB+βC, and is the performance foundation of all linear algebra operations such as high-dimensional evolution, SVD, and QR. MKL (Intel Math Kernel Library) is Intel's math library deeply optimized for its own CPUs, capable of fully utilizing instruction sets like AVX-512 and multi-core caches. VPU's switch from pure NumPy to MKL was the key to the dramatic drop from 481ms to 1.28ms at the v10.10.2 stage, because NumPy's default backend has low utilization on small-matrix batch operations, while MKL can drive these GEMMs close to the memory bandwidth limit—which also explains why the subsequent P4a "eliminating 63% memory bandwidth bottleneck" could deliver another leap.
Layer 3: Hermes Agent (LangChain + Ollama)
VPU is wrapped as a LangChain tool that the LLM agent can call on its own initiative. Inside the tool, it selects rank_ratio based on the logic_complexity parameter (low=0.05, medium=0.1, high=0.15), generates the energy landscape H_env for the problem space, then runs the specified number of parallel evolution steps, and finally returns JSON containing equivalent FPS, von Neumann entropy, and convergence insights.
The agent uses Ollama's holo-9b-bf16 model, paired with the soul.md system prompt that explicitly tells it when to call VPU—multi-branch parallel path simulation, game tree search, extremely complex problems requiring "subconscious" parallel trial-and-error—and when not to call it: simple text Q&A, basic arithmetic, common-sense retrieval.
LangChain tool calling means registering external functions (like the VPU wrapped here) as "tools" the LLM can autonomously invoke. Based on the system prompt and current context, the LLM outputs a structured call request (function name + parameters), which the runtime executes and then feeds the result back to the model as text or JSON for continued reasoning. The key to the Hermes agent is precisely a soul.md with clearly defined boundaries: telling the model which scenarios (multi-branch parallel path simulation, game tree search) should invoke VPU, and which (simple Q&A, arithmetic, common-sense retrieval) should not. Combined with Ollama's local inference (the holo-9b-bf16 model), this allows the entire "subconscious accelerator" to run in a local closed loop without relying on cloud APIs, with VPU as the sole heavy-compute node triggered on demand.
Layer 4: Smart Cooling Daemon (C++ + SYCL)
Running matrix operations at 3000 FPS generates considerable heat. smart_cooling_daemon.cpp is a SYCL-based background daemon: it reads CPU temperature via WMI, runs DMA stress threads and a TLL spiral engine, and dynamically adjusts load to keep temperature under control. Compiled with icpx -fsycl -O3 -std=c++17.
Benchmarks: Tracing the Path to 1490x Speedup
Measured data (dim=256 and dim=512):
| Metric | dim=256 | dim=512 |
|---|---|---|
| Average latency | 0.323 ms | 0.324 ms |
| P50 latency | 0.060 ms | 0.053 ms |
| P99 latency | 1.814 ms | 5.496 ms |
| Max latency | 2.837 ms | 8.496 ms |
| Equivalent FPS | 3099 | 3088 |
| Rank | 25 | 25 |
The performance evolution path clearly shows the order-of-magnitude change from each optimization: v10.8.2 (SVD caching) → 481ms; v10.10.2 (MKL + streaming) → 1.28ms; v10.12 (QR + GEMM) → 1.20ms; v10.13 (P4 lazy H_eff + caching + pre-allocation) → 0.323ms. From v10.8.2 to v10.13, a total of 1490x speedup. Compared to the full-rank (no low-rank approximation) approach, 200 steps at dim=256 drops from 4249ms to 160ms, a 26.44x improvement.
Agent's Actual Runtime Flow
When the agent receives a complex query: the LLM reads the query and determines serial reasoning is insufficient → calls vpu_parallel_reasoning(dim=256, steps=150, logic_complexity="high") → VPU completes 150 steps of parallel evolution in about 50ms → returns JSON containing entropy, FPS, and convergence metrics → the LLM interprets the metrics and generates a human-readable answer.
ADE: A Formula-Traceable Tetris AI
The workspace also includes ADE (Aether Decision Engine)—a Tetris decision system integrated with VPU. Every decision is auditable: the ADEDecision data class records piece type, rotation, column position, confidence, margin, probabilities, formula chain (e.g., ["option_scoring", "softmax", "argmax"]), triggering rules, and a complete audit trail. The scoring flow is option_scoring → softmax → argmax → margin, where margin is the top-2 score difference, representing confidence. This pattern isn't limited to Tetris—it applies to any auditable AI decision scenario where you need to know "why this was chosen" rather than just "what was chosen."
The meaning of softmax, argmax, and margin: softmax converts a set of raw scores (logits) into a probability distribution summing to 1, p_i = exp(z_i)/Σexp(z_j), expressing the relative preference for each candidate action; argmax takes the option with the highest probability or score as the final decision; margin is usually defined as the score difference between the best and second-best options (top-2 gap), quantifying the model's "confidence" in this choice. ADE records the entire chain of option_scoring → softmax → argmax → margin along with triggering rules into ADEDecision, so any move can be traced back to specific formulas and intermediate values. The value of this "explainable decision chain" pattern is that it turns explainability from vague natural language explanations into reproducible, auditable formal records, applicable to any decision system that needs to answer "why this was chosen, not just what was chosen"—such as scheduling, risk control, and autonomous driving strategy selection.
Key Takeaways and Future Directions
LLMs and parallel engines are complementary: the LLM handles language understanding and decision framing, while VPU handles parallel exploration—neither can replace the other. The power of low-rank approximation is that at dim=512, dropping from rank=dim to rank=25 yields a 26x speedup with minimal accuracy loss. Memory allocation is a performance killer—just pre-allocating RK4 buffers alone contributes a substantial FPS improvement. Lazy computation eliminates 63% of the memory bandwidth bottleneck.
The complete Ai_Brain workspace includes the VPU engine, LangChain wrapper, Hermes agent, soul.md personality protocol, ADE decision engine, Tetris game engine, SYCL cooling daemon, performance testing tools, and an AES-256-GCM encrypted credential library.
Next steps: embedding-based H_env generation (feeding real problem embeddings into the Hamiltonian), a SYCL GPU-accelerated version (migrating from NumPy to true GPU kernels), and VPU-in-the-loop agent training (using entropy as a reward signal). The author's judgment is: the future of AI agents isn't just bigger LLMs, but LLMs with better tools—and sometimes that tool is a parallel evolution engine running at 3000 FPS.
One-line Summary
VPU achieves 3000 FPS parallel exploration on integrated graphics using low-rank quantum-inspired evolution, serving as a 'subconscious accelerator' for LLM agents.
Paragraph Summary
The article introduces VPU v10.13, built by developer logout2login—a high-dimensional parallel evolution engine running on an ordinary Intel Iris Xe integrated GPU, operating on a low-rank approximation of a Hermitian Hamiltonian, evolving states via RK4 integration and measuring convergence with von Neumann entropy. Its P4-series lazy H_eff optimizations (skipping lightweight steps, caching bases, pre-allocating buffers, auto-detecting environment changes) push latency down to 0.32ms, hitting 3000+ equivalent FPS at dim=512 and achieving a 1490x speedup over v10.8.2. VPU is wrapped as a LangChain tool and integrated into the Hermes agent, forming a complementary architecture of 'LLM serial thinking + VPU parallel exploration.' The article also covers the formula-traceable ADE Tetris decision engine and future directions including embedding-based H_env generation, SYCL GPU acceleration, and VPU-in-the-loop training, with code open-sourced under the MIT license.
Related articles

Chain of Thought Isn't Just for AI: How Humans Can Use CoT to Improve Thinking Quality
Chain of Thought isn't just a prompt trick for large models. Starting from a Hacker News discussion, this article analyzes why CoT works for human thinking too, breaks down actionable ways to transfer it, and highlights the key differences between human CoT and machine CoT.
Cloudflare Teams Up with OpenAI: Closi…
Cloudflare Teams Up with OpenAI: Closing the Loop from Vulnerability Discovery to Defense with AI
Cloudflare uses OpenAI Daybreak to investigate security vulnerabilities and generate reviewable remediation plans, while developers use Codex to boost coding efficiency and quality.

Orca Multi-Agent Orchestration in Practice: A Guide to Parallel Collaboration with Claude and Codex
Orca is Stable AI's free open-source agent workbench supporting 34 agents like Claude Code and Codex in parallel. Learn its Git worktree isolation, multi-model orchestration, and mobile management.