The Era of Teranode per second movegeneration is here - Gigantua Warp

[mysammoore]

What I'd genuinely like to know is where you see this going as an engine, specifically what the eval does, because that's the part of the picture I can't reconstruct from the post. A perft tree is pure movegen, every child is needed and nothing a sibling returns changes what happens next, which is exactly what a warp wants. The moment there's an evaluation and a search deciding what not to look at, the node stops being a movegen problem. My engine spends about 3% of a node on movegen and about 72% on the NNUE eval, and the search is alpha-beta where a cutoff is divergence by definition, so from where I sit teranodes of movegen don't touch the thing that decides strength. So is the intent that the eval runs on the GPU as well, batched across the warp, and the search changes shape to feed it, or is the intent that this stays a perft and enumeration machine and "engine" just means the movegen core? Both are legitimate, I just can't tell which one you're building toward, and it's a very different project depending on the answer. The dedup side is the part that looks like it could carry over regardless, 65x at ply 8 is a lot more transposition than I would have guessed.