From 94b50c61b32a4f626fcdbc5e167cac1e2cd8e5bc Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 14 Jul 2022 16:09:48 -0400 Subject: [PATCH] comment --- ..._8_e041fcd11c50d47eada124368a5bb7b5._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_8_e041fcd11c50d47eada124368a5bb7b5._comment 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 index 0000000000..72e9a48acf --- /dev/null +++ b/doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_8_e041fcd11c50d47eada124368a5bb7b5._comment @@ -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. +"""]]