| Metric | Kuzu v0.135 (unstable) | Kuzu v0.136 (fixed) | Improvement | | --- | --- | --- | --- | | Average query latency | 340 ms | 212 ms | | | Memory usage (peak) | 5.2 GB | 1.8 GB | 65% reduction | | Multi-threaded throughput | 1,200 ops/sec | 2,450 ops/sec | 104% increase | | Crash rate (24 hours) | 1 crash per 6 hours | 0 crashes | 100% stable |
Fix: The new concurrency model defaults to optimistic locking. If you have extremely high write contention, set kuzu.optimistic_retries = 5 in your config file. For pure read-heavy workloads, enable kuzu.read_only = true .
The changelog highlights a new optimistic concurrency control mechanism using 64-bit atomic timestamps. The team also removed the problematic spinlock implementation in favor of a mutex pool. Internal stress tests (100 threads performing 10,000 writes each) now show zero conflicts and 99.999% write atomicity. 3. The JSON Parsing Regression (Issue #910) Version 0.135 broke support for nested JSON objects exceeding three levels. Developers relying on Kuzu’s built-in JSON extractor received malformed outputs or outright segfaults. This was particularly painful for those using Kuzu as an ETL (Extract, Transform, Load) tool. kuzu v0 136 fixed
If you have been waiting for a sign to adopt Kuzu—or to return after the v0.135 fiasco—the time is now. Download today, run your workloads, and experience the stability that should have been there from the start. Have you tested Kuzu v0.136 fixed in your environment? Share your results in the comments below or contribute to the official Kuzu GitHub repository. Found another bug? The maintainers are prioritizing reports against this version above all others.
reintroduces a recursive descent parser with enhanced stack overflow protection. The new parser handles arbitrarily deep JSON (tested up to 128 levels) and improves parsing speed by 18% compared to v0.134 (the last stable version). Additionally, error messages now include line and column numbers for malformed JSON, drastically improving debuggability. 4. Windows File Path Handling (Issue #915) Cross-platform users on Windows experienced a bizarre bug: Kuzu would fail to open any file with a space in its path (e.g., C:\My Data\kuzu.db ). The issue was an improper use of string escaping in the file URI handler. The kuzu v0.136 fixed patch replaces custom path logic with the standard std::filesystem::path class, ensuring full Unicode and whitespace support across Windows, Linux, and macOS. Performance Benchmarks: Before and After Numbers do not lie. The Kuzu team released a public benchmark comparing v0.135 (buggy) vs. v0.136 fixed on a standard dataset (TPC-H-like workload with 10 million records). | Metric | Kuzu v0
Fix: You are trying to load a custom plugin compiled against v0.135. Recompile the plugin against the v0.136 headers.
Fix: Roll back using your backup, then run kuzu dump on v0.135 to export raw data. Install v0.136 fresh and run kuzu load from the dump. This circumvents any on-disk format quirks. Final Verdict: Is Kuzu v0.136 Fixed Ready for Production? Yes, unequivocally. the transparent changelog
Where v0.135 felt like a beta product, v0.136 fixed exudes the confidence of a production-grade system. The careful attention to cross-platform details, the transparent changelog, and the rigorous benchmarking show a maturing project ready for wider enterprise adoption.