feat(flatfs): default to sync=false (#10632)
Marcin Rataj committed
Dec 20, 2024 at 01:14 UTC
f2c190535c0ea445535270ef1c21496c432ac17c
3 files changed
+10
-1
config/init.go
+1
-1
@@ -173,7 +173,7 @@ func flatfsSpec() map[string]interface{} {
173
"child": map[string]interface{}{
174
"type": "flatfs",
175
"path": "blocks",
176
- "sync": true,
176
+ "sync": false,
177
"shardFunc": "/repo/flatfs/shard/v1/next-to-last/2",
178
},
179
},
docs/changelogs/v0.33.md
+7
@@ -8,6 +8,7 @@
8
- [🔦 Highlights](#-highlights)
9
- [Bitswap improvements from Boxo](#bitswap-improvements-from-boxo)
10
- [Using default `libp2p_rcmgr` metrics](#using-default-libp2p_rcmgr--metrics)
11
+ - [Flatfs does not `sync` on each write](#flatfs-does-not-sync-on-each-write)
12
- [`ipfs add --to-files` no longer works with `--wrap`](#ipfs-add---to-files-no-longer-works-with---wrap)
13
- [New options for faster writes: `WriteThrough`, `BlockKeyCacheSize`, `BatchMaxNodes`, `BatchMaxSize`](#new-options-for-faster-writes-writethrough-blockkeycachesize-batchmaxnodes-batchmaxsize)
14
- [MFS stability with large number of writes](#mfs-stability-with-large-number-of-writes)
@@ -29,6 +30,12 @@ Bespoke rcmgr metrics [were removed](https://github.com/ipfs/kubo/pull/9947), Ku
30
This makes it easier to compare Kubo with custom implementations based on go-libp2p.
31
If you depended on removed ones, please fill an issue to add them to the upstream [go-libp2p](https://github.com/libp2p/go-libp2p).
32
33
+#### Flatfs does not `sync` on each write
34
+
35
+New repositories initialized with `flatfs` in `Datastore.Spec` will have `sync` set to `false`.
36
+
37
+The old default was overly conservative and caused performance issues in big repositories that did a lot of writes. There is usually no need to flush on every block write to disk before continuing. Setting this to false is safe as kubo will automatically flush writes to disk before and after performing critical operations like pinning. However, we still provide users with ability to set this to true to be extra-safe (at the cost of a slowdown when adding files in bulk).
38
+
39
#### `ipfs add --to-files` no longer works with `--wrap`
40
41
Onboarding files and directories with `ipfs add --to-files` now requires non-empty names. due to this, The `--to-files` and `--wrap` options are now mutually exclusive ([#10612](https://github.com/ipfs/kubo/issues/10612)).
docs/datastores.md
+2
@@ -29,6 +29,8 @@ The shardFunc is prefixed with `/repo/flatfs/shard/v1` then followed by a descri
29
}
30
```
31
32
+- `sync`: Flush every write to disk before continuing. Setting this to false is safe as kubo will automatically flush writes to disk before and after performing critical operations like pinning. However, you can set this to true to be extra-safe (at the cost of a slowdown when adding files).
33
+
34
NOTE: flatfs must only be used as a block store (mounted at `/blocks`) as it only partially implements the datastore interface. You can mount flatfs for /blocks only using the mount datastore (described below).
35
36
## levelds