| Database | Query: Complex 6-hop Friend Recommendation | Memory Peak | Query Time | | :--- | :--- | :--- | :--- | | | 45.2 seconds | 14.2 GB (OOM risk) | Slow | | Kuzu v0.1.2 | 3.1 seconds | 4.1 GB | Fast | | DuckDB (via graph extension) | 22.4 seconds | 8.2 GB | Medium | | Neo4j (Community, embedded via Bolt) | 5.2 seconds (plus network RTT) | 12 GB | Fast | | SQLite (Recursive CTE) | 98 seconds | 2 GB (but fails on deep hops) | Impractical |
A major overhaul was implemented for evaluating complex recursive joins (patterns with the Kleene star * ). Prior implementations were slow, but the new engine introduced parallelized execution, dense data structures, and significant memory optimizations. This allowed efficient handling of operations like *1..10 (neighbors 1 to 10 steps away) and SHORTEST paths, which are notoriously expensive for most databases.
To make your Cypher queries run "better":
Scanning JSON data is now more efficient, speeding up ingestion and integration workflows. kuzu v0 120 better
Architectural Comparison: Kuzu v0.12.0 vs. Traditional Graph Servers
: A major highlight of the "better" versioning was the early integration of vector capabilities, allowing Kuzu to act as a hybrid Graph-Vector database, which is essential for modern RAG (Retrieval-Augmented Generation) applications. Why v0.2.0 is Considered "Better"
You can now run vector search with arbitrary Cypher queries . This means you can combine traditional graph traversals (e.g., "find all neighbors of node X") with vector similarity searches (e.g., "within a specific type and that have an embedding similar to query Y") directly in the same query. | Database | Query: Complex 6-hop Friend Recommendation
Let’s break the hype cycle.
: Re-examine your long Cypher queries. Newer versions improve the cost-based optimizer, which may allow you to simplify complex WITH and MATCH patterns. 3. Infrastructure and Environment
Upgrading to v0.12.0 is straightforward. However, please note that this release introduces changes to the on-disk storage format to support the new optimizer features. To make your Cypher queries run "better": Scanning
: Version 0.2.0 introduced a redesigned query execution engine. For complex graph traversals (like multi-hop joins), benchmarks showed performance improvements ranging from 2x to 10x faster than the 0.1.x series.
Summary
We are thrilled to announce the release of !
Comparative benchmarks validate this claim. The blog "The Data Quarry" conducted a detailed benchmark, pitting Kuzu against the widely used Neo4j Community Edition on a social network dataset. The results were stunning: