https://hypercrux.com/tags/roadmap/ Recent content in Roadmap on HyperCrux.com Hugo en-us Wed, 07 Oct 2026 00:00:00 +0000 https://hypercrux.com/how-long-a-new-hypercrux-engine-in-c-would-take-four-to-six-weeks-phase-by-phase/ Wed, 07 Oct 2026 00:00:00 +0000 https://hypercrux.com/how-long-a-new-hypercrux-engine-in-c-would-take-four-to-six-weeks-phase-by-phase/ <p>The <a href="https://github.com/hypercrux/hypercrux/blob/main/BETA.md">Beta plan</a> describes a new database engine for HyperCrux, written in C, with all four handles built in. A plan like that needs a time estimate before anyone decides whether to start it. Here it is: about 19 to 30 working days of development to reach the Beta gate, which comes to roughly four to six weeks of calendar time with a working session most days. A first working version with all four handles would come in about a week.</p> https://hypercrux.com/three-ways-to-make-hypercrux-faster-a-c-search-loop-altsql-db-underneath-or-a-new-engine-in-c/ Wed, 07 Oct 2026 00:00:00 +0000 https://hypercrux.com/three-ways-to-make-hypercrux-faster-a-c-search-loop-altsql-db-underneath-or-a-new-engine-in-c/ <p>HyperCrux 0.1 is a Go library and command on top of SQLite, and it&rsquo;s quick at the sizes it was built for. In the recorded benchmarks on a two-core cloud machine, a get by key takes 18 microseconds and a walk one link out 43 microseconds. A search among 100,000 vectors of 384 values takes 0.41 seconds. The question that comes up next is how much faster it could get, and what each step would cost.</p>