Backend
Lantern: Finding Committable Transactions via Back-Propagation on DAGs
arXiv cs.DC0 views
arXiv:2609.03315v2 Announce Type: replace Abstract: Existing concurrency control protocols either introduce nondeterminism, resulting in a serial execution-replay dependency between primary and replica nodes, or rely on impractical prior knowledge of transaction read-write sets. In this paper, we present Lantern, a deterministic concurrency control protocol tailored for high-performance transaction processing systems operating without prior knowledge. The key insight of Lantern is that all zero-out-degree transaction vertices in the local dependency graph can be safely committed in ascending order using an overwrite-permissive strategy. We further introduce a novel Back-Propagation mechanism that iteratively propagates dependency states from sink to source vertices to identify additional committable transactions. We also propose Conflict-Free Batch Selection (CFBS) for read-modify-write intensive scenarios. We integrate Lantern into the open-source blockchain platform ChainMaker. Extensive evaluations on YCSB and SmallBank benchmarks demonstrate that Lantern achieves up to a 4.2x throughput speedup over Aria and improves the throughput of ChainMaker's execution layer by at least 2.2x.
Source:https://arxiv.org/abs/2609.03315PreviousTwig: Parallel and Memory-Efficient Tree Speculative Decoding for Hybrid-Attention LLMsNextRandom Centres and the $\varepsilon$-Dependence of Constant-Round Planar Domination
Related posts

We rewrote zg in Rust, cutting indexing time by 65% and peak memory by 53%
0Rust Users Forum

Michiu (now at v0.2.2!): An experimental GUI library for Windows focused on DirectComposition, wgpu, and DOD
0Rust Users Forum
Mocking a 410 Gone for a Retired Resource vs a Plain 404
0dev.to
Three MCP Python SDK Advisories, and the One an Upgrade Will Not Fix
0dev.to
We Benchmarked GPT-Image-2.6 Native <svg> Output: Path Counts, Cost & Real Edge Cases
0dev.to
When an MCP Tool Needs a Missing Value: Elicitation vs Failing the Call
0dev.to