Kuzu V0 136 Fixed _verified_

If you are moving between versions, keep these best practices in mind: Export/Import Requirement:

| Workload Type | v0.136 (Broken) | v0.136 (Fixed) | Improvement | |---------------|----------------|----------------|-------------| | 2-hop friends | 124 ms (unstable) | 118 ms | +5% stability | | 5-hop path query | Crash (100%) | 1,420 ms | | | Bulk insert (1M edges) | 8.2 sec (leaky) | 7.9 sec | +3.7% | | Memory peak (10 concurrent queries) | 2.4 GB (fragmented) | 1.9 GB | -21% | kuzu v0 136 fixed

After several more hours of intense coding and testing, the fix was ready. The team cautiously rolled out the update, tagged as "kuzu v0.136 fixed," to a subset of users first. The feedback was overwhelmingly positive; the bug was gone, and the stability of Kuzu had improved noticeably. If you are moving between versions, keep these

Capable of handling graphs with hundreds of millions of nodes and billions of edges. Capable of handling graphs with hundreds of millions

Fixed issues related to recovering from corrupted Write-Ahead Logs (WAL) and ensuring is properly called on macOS/iOS to prevent data loss. Graph Operations:

If you saw "v0.136" in a specific repository or community thread, it might be an internal build or a community fork. The official releases can always be verified on the Kùzu GitHub Releases page . v0.7.1 (Latest as of early 2024).