LayerFS v0.1.4 — storage efficiency Developer Preview
LayerFS v0.1.4 — storage efficiency Developer Preview
v0.1.4 adds packed SQLite storage, native FULL/PREFIX representations, bounded
shared Init/Commit publication, and reuse of authenticated Init comparison bytes.
The accepted full157 observation uses 184,582,144 allocated bytes, 15.374%
less than its 218,116,096-byte supplemental control. Adjacent duplicate-heavy
Init observations improve by 80–82% against the prior R26 candidate while
preserving exact collision checks. These are scoped observations, not universal
performance guarantees or statistically established distributions.
Validation covers 198 performance cases, 226 routine proofs, supplemental
small-file/SDK/FUSE workloads, 157 performance states and 157 retained-history
proofs. The optional 600-second endurance proof was not run.
Known tradeoffs: substantial regressions versus v0.1.3 remain. Three absolute
latency targets miss; the four historical Git comparisons are INELIGIBLE and
the current overall report remains INCOMPLETE. Owner acceptance does not turn
those outcomes into passes. Full157 historical verification also took longer
than the prior candidate. Read the complete tables and measurement boundaries.
Upgrade boundary: create a new schema-7 Store. Supported development
schema-6 Stores retain the legacy format. Released v0.1.3/schema-5 Stores are
not migrated or opened; preserve them with their original binaries. Directory
import starts new history. Use matching SDK/owner/daemon builds.
This is a source-only Developer Preview, not production storage. Crash and
power-loss durability are not promised. The source assets and checksums are attached to the GitHub release.
See the versioned manual, accepted-tradeoff record and full terminal evidence
in the accompanying source tree.
The included issue #98 Workspace repair is fully qualified: adjacent Commit time improved 37.8%, final allocated storage is unchanged, and all benchmark/proof/full157 checks passed. Final .venv observations and higher unpaired full157 wall times are reported explicitly. Remaining historical performance misses and four ineligible Git comparisons stay visible.
Every benchmark family and case. Existing qualified results were reused; no benchmark was rerun for publication.
Existing benchmark results by family
Times below are descriptive sums of individual case timers, not campaign wall time or statistical speedup estimates. Positive changes mean slower than the eligible published v0.1.3 checkpoint.
| Family | Performance cases | Passing proofs | v0.1.3 seconds | v0.1.4 seconds | Change |
|---|---|---|---|---|---|
| payload_create_read | 8 | 8 | 4.179502 | 3.872964 | -7.33% |
| dedup_workspace_reuse | 14 | 14 | 15.874997 | 14.074111 | -11.34% |
| dedup_cross_file | 10 | 10 | 1.402381 | 3.154912 | +124.97% |
| dedup_cdc_locality | 20 | 21 | 1.484589 | 3.187850 | +114.73% |
| edit_length_preserving | 12 | 12 | 0.082806 | 0.119696 | +44.55% |
| edit_length_changing | 32 | 32 | 0.230456 | 0.306447 | +32.97% |
| edit_canonical_chunk_count | 12 | 12 | 0.092536 | 0.135438 | +46.36% |
| init_namespace | 4 | 4 | 3.053609 | 4.903439 | +60.58% |
| store_footprint | 6 | 6 | 8.156506 | 12.273350 | +50.47% |
| tiny_file_churn | 20 | 20 | 8.529795 | 8.996516 | +5.47% |
| namespace_mutation | 4 | 4 | 0.314367 | 0.429782 | +36.71% |
| directory_construction_traversal | 12 | 12 | 7.628812 | 9.710653 | +27.29% |
| workspace_change_locality | 16 | 16 | 10.971227 | 13.240867 | +20.69% |
| dedup_branch_history | 20 | 20 | 47.049815 | 55.856741 | +18.72% |
| git_tool_workflow | 4 | 4 | — | 8.877153 | INELIGIBLE |
| mixed_load_bearing | 4 | 4 | 8.559964 | 8.592193 | +0.38% |
| workspace_reliability | 0 | 27 | — | — | — |
Elapsed comparison labels: 49 SEVERE, 95 REVIEW, 31 OBSERVED_INCREASE, 19 NO_INCREASE, 4 INELIGIBLE. Execution success is separate from performance acceptance. The overall comparison report remains INCOMPLETE.
Full157 retained-state storage: 184,582,144 B versus 218,116,096 B, a 15.374359% reduction. The supplemental storage control is not the published v0.1.3 performance baseline. Full157 performance/verification wall observations were 481.975846875 s / 613.815488042 s, higher than the previous 447.246954625 s / 545.826543958 s; these are unpaired historical observations.
Source and evidence identities
Qualified product source: 9cfb4be477116646258ea0621280ed13b1824c6d. Documentation and packaging updates preserve that production code.
Host benchmark SHA-256: 47b4d44e3e961f3b6a57d2c18dc6d195973133dbdfb87681a55f1b8e07abe3a2.
Sealed benchmark image: sha256:42eb806fcfe9db1dc28098eb423340de3e4eaf81fd487389128305e65606d347. These are benchmark identities, not newly published binary assets.
Immutable qualified evidence · Versioned manual · All 198 case results.
Released commit: 101fa273d815f3aaedb0e06ba0de7b0777d83def. Annotated tag object: c1c3830c29a3dbece4a490c06e922f1f81295091. Final PR CI: 34338286986. Final merged tree equals qualified PR #99's tree; production code matches the qualified source.
Six source-only assets were verified against the tagged Git tree (4,161 source members; 2,888 selected evidence members). SHA256SUMS covers the other five assets. No prebuilt executables, public runtime image or crates.io publication is included.