comment
authorJoey Hess <joeyh@joeyh.name>
Thu, 14 Jul 2022 20:09:48 +0000 (16:09 -0400)
committerJoey Hess <joeyh@joeyh.name>
Thu, 14 Jul 2022 20:09:48 +0000 (16:09 -0400)
doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_8_e041fcd11c50d47eada124368a5bb7b5._comment [new file with mode: 0644]

diff --git a/doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_8_e041fcd11c50d47eada124368a5bb7b5._comment b/doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_8_e041fcd11c50d47eada124368a5bb7b5._comment
new file mode 100644 (file)
index 0000000..72e9a48
--- /dev/null
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 8"""
+ date="2022-07-14T19:50:30Z"
+ content="""
+I think that CoW and append could indeed speed it up. An append on a CoW
+filesystem should be able to keep the original file without copying it, and
+just add a new block for the append to the other file. I did a quick test
+on btrfs, starting with a 100 mb file, making a cp --reflink, and
+appending to it. All operations were less than 10 ms.
+
+----
+
+The buffering in memory would be while the process was running, then it
+would commit it to the git-annex branch. So if no other process needs to
+see that data while the process is running, you'd be ok.
+"""]]