Skip to content

Commit d7e81d7

Browse files
committed
feat(ipip-0499): document efficiency benefits of modern profile parameters
add user benefit explaining why 1 MiB chunks with 1024 links per node results in shallower DAG trees, fewer total nodes, faster seeking, and reduced DHT announcement overhead compared to legacy 256 KiB/174 params
1 parent b832bcc commit d7e81d7

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

src/ipips/ipip-0499.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,14 +170,20 @@ This profile documents the default UnixFS DAG construction parameters used by Ku
170170

171171
### User benefit
172172

173-
Profiles provide 3 key advantages for working with content-addressed data:
173+
Profiles provide key advantages for working with content-addressed data:
174174

175175
1. **Predictable, deterministic behavior:** Profiles restore intuitive hash-like behavior: identical input data always produces identical CIDs, regardless of which implementation generates them.
176176

177177
2. **Lightweight verification:** Users can verify content without needing to rely on additional merkle proofs or CAR files.
178178

179179
3. **Simplified workflow:** Users can select a profile and automatically get consistent CIDs across all implementations, without needing to configure or understand the underlying parameters.
180180

181+
4. **Improved efficiency:** The `unixfs-v1-2025` profile uses 1 MiB chunks with 1024 links per node, compared to the legacy 256 KiB chunks with 174 links. This results in:
182+
- Shallower DAG trees (3 levels for a 1 TiB file vs 4 levels with legacy parameters)
183+
- Approximately 4x fewer total nodes for the same content
184+
- Faster random access and seeking in large files (fewer round-trips to traverse the tree)
185+
- Fewer CIDs to announce, reducing stress on public good routing infrastructure such as the Amino DHT
186+
181187
### Compatibility
182188

183189
UnixFS data encoded with the CID profiles defined in this IPIP remains fully compatible with existing implementations, since it conforms to the [UnixFS specification](https://specs.ipfs.tech/unixfs/).

0 commit comments

Comments
 (0)