mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-10-19 12:34:29 +02:00
pingqiuandClaude Opus 4.6
676539d3b9
testrunner-roadmap.md: P0-P3 feature plan for multi-version comparison, Ceph adapter, result tracking, cluster templates, debug mode. dm-stripe-two-server.yaml: proven Linux dm-stripe across 2 sw-block volumes on 2 servers. Results: single=42K IOPS → striped=79K IOPS (1.87x). Data integrity verified via md5. Zero sw-block code changes needed. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
sw-block
Private WAL V2 and standalone block-service workspace.
Purpose:
- keep WAL V2 design/prototype work isolated from WAL V1 production code in
weed/storage/blockvol - allow private design notes and experiments to evolve without polluting V1 delivery paths
- keep the future standalone
sw-blockproduct structure clean enough to split into a separate repo later if needed
Suggested layout:
design/: shared V2 design docsprototype/: code prototypes and experiments.private/: private notes, phase development, roadmap, and non-public working material
Repository direction:
- current state:
sw-block/is an isolated workspace insideseaweedfs - likely future state:
sw-blockbecomes a standalone sibling repo/product - design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths